Low cost LED driver with improved serial bus

ABSTRACT

An LED driver IC for driving external strings of LEDs includes a prefix register and a data register connected in series with each other and with the prefix and data registers in other driver ICs. The prefix and data registers of the driver ICs are connected in a daisy chain arrangement with an interface IC. The interface IC loads data identifying a functional latch into the prefix register and data defining a functional condition into the data register of each driver IC. The data in the data register is then transferred to the functional latch to control the functional condition within the LED driver IC.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 13/347,658,filed Jan. 10, 2012, which is a continuation of application Ser. No.13/346,647, filed Jan. 9, 2012, now U.S. Pat. No. 8,779,696, whichclaims priority to Provisional Application No. 61/550,539, filed Oct.24, 2011, each of which is incorporated herein by reference in itsentirety.

This application is related to the following applications, each of whichis incorporated herein by reference in its entirety: application Ser.No. 13/346,625, filed Jan. 9, 2012, titled Low Cost LED Driver withIntegral Dimming Capability, now U.S. Pat. No. 9,232,587; andapplication Ser. No. 13/346,659, filed Jan. 9, 2012, titled SerialLighting Interface With Embedded Feedback, now U.S. Pat. No. 9,288,861.

BACKGROUND

Field of the Invention

This invention relates to semiconductor devices and circuits and methodsfor driving LEDs in lighting and display applications.

Discussion of Related Art

LEDs are increasingly being used to replace lamps and bulbs in lightingapplications including providing white light as a back light in colorliquid crystal displays (LCD) and high definition televisions (HDTV).While LEDs may be used to uniformly light the entire display,performance, contrast, reliability, and power efficiency are improved byemploying more than one string of LEDs and to drive each string to adifferent brightness corresponding to the portion of the display thatthe particular LED string illuminates. “Local dimming” refers tobacklighting systems capable of such non-uniform backlight brightness.The power savings in such systems can be as high as 50% as compared withLCDs employing uniform backlighting. Using local dimming, LCD contrastratios can approach those of plasma TVs.

To control the brightness and uniformity of the light emitted from eachstring of LEDs, special electronic driver circuitry must be employed toprecisely control the LED current and voltage. For example, a string of“m” LEDs connected in series requires a voltage equal to approximately3.1 to 3.5 (typically 3.3) times “m” to operate consistently. Supplyingthis requisite voltage to a LED string generally requires a step-up orstep-down voltage converter and regulator called a DC-to-DC converter orswitch-mode power supply (SMPS). When a number of LED strings arepowered from a single SMPS, the output voltage of the power supply mustexceed the highest voltage required by any of the strings of LEDs. Sincethe highest forward voltage required cannot be known a priori, the LEDdriver IC must be intelligent enough to dynamically adjust the powersupply voltage using feedback.

In addition to providing the proper voltage to the LED strings, thebacklight driver ID must precisely control the current conducted in eachstring to a tolerance of ±2%. Accurate current control is necessarybecause the brightness of an LED is proportional to the current flowingthrough it, and any substantial string-to-string current mismatch willbe evident as a variation in the brightness of the LCD. Aside fromcontrolling the current, local dimming requires precise pulse control ofLED illumination, both in timing and duration, in order to synchronizethe brightness of each backlight region, zone, or tile to thecorresponding image in the LCD screen.

The prior art's solutions to the need for local dimming limit displaybrightness and are costly. For example, early attempts to integrate LEDdriver circuitry with multiple channels of high-voltage current sinktransistors were problematic because mismatch in the forward voltage ofthe LED strings resulted in excessive power dissipation and overheating.Attempts to minimize power dissipation by lowering the current in theLEDs and limiting the number of LEDs in a string (for betterchannel-to-channel voltage matching) proved uneconomical, requiring moreLED strings and a greater number of channels of LED drive. Thus the fullintegration approach to LED backlight driver systems has been limited tosmall display panels or very expensive “high-end” HDTVs.

Subsequent attempts to reduce overall display backlight costs by usingmultichip approaches sacrificed necessary features, functionality, andeven safety.

For example, the prior art multichip system for driving LEDs shown inFIG. 1 comprises backlight controller IC 6 which drives multiplediscrete current sink transistors 4A-4Q and high-voltage protectivedevices 3A-3Q. The backlight comprises sixteen LED strings 2A-2Q(collectively referenced LED strings 2). Each of LED strings 2A-2Qcontains “m” series-connected LEDs. In practice, the number of LEDs ineach string can range from two to sixty. Each LED string has its currentcontrolled through one of discrete current sink MOSFETs 4A-4Q,respectively. Backlight controller IC 6 sets the current in each LEDstring in response to instructions from a backlight microcontroller μC7, which are communicated through a high-speed, expensive, serialperipheral interface (SPI) bus 12. Microcontroller μC 7 receives videoand image information from a scalar IC 8 in order to determine theproper lighting levels needed for each of LED strings 2A-2Q.

LED strings 2A-2Q are powered by a common LED power supply rail 11,which is biased at a voltage +V_(LED) by switch-mode power supply (SMPS)9. The voltage +V_(LED) is generated in response to a current-sensefeedback signal (CSFB) 10 from control IC 6. Supply voltages vary withthe number of LEDs “m” connected in series and may range from 35 voltsfor strings of ten LEDs up to 150 volts for strings of 40 LEDs. Discreteprotective devices 3A-3Q, typically high-voltage discrete MOSFETs, areoptionally employed to clamp the maximum voltage present across thecurrent sink transistors 4A-4Q, especially for operation at highervoltages, e.g. over 100V.

In the system shown in FIG. 1 each component is a discrete device, in aseparate package, requiring its own pick-place operation to position andmount it on its printed circuit board.

Each set of discrete components, along with the corresponding string ofLEDs, is repeated “n” times for an “n” channel driver solution. Forexample, in addition to SMPS 9, the 16-channel backlight system shown inFIG. 1 requires 34 components, namely microcontroller 7, ahigh-pin-count backlight controller IC 6, 16 current sink transistors4A-4Q and 16 protective devices 3A-3Q, to facilitate local dimming inresponse to video information generated from scalar IC 8. This solutionis complex and expensive.

Aside from requiring the assembly of a large number of discretecomponents, i.e. a high bill of materials (BOM) count, the package costof high pin count package 6 is substantial. The need for such a largenumber of pins is illustrated in the circuit diagram of FIG. 2A, whichillustrates in greater detail one of the channels of LED driver systemshown in FIG. 1. As shown each channel includes a string 21 of “m”series-connected LEDs, a protective cascode-clamp MOSFET 22 with anintegral high-voltage circuiting diode 23, a current sink MOSFET 24, anda current-sensing I-Precise gate driver circuit 25.

The active current sink MOSFET 24, implemented as a discrete componentcontrolled by the interface IC 6, comprises a power MOSFET, preferably avertical DMOSFET, having gate, source and drain connections. I-Precisegate driver circuit 25 senses the current in current sink MOSFET 24 andprovides it with the requisite gate drive voltage to conduct a preciseamount of current. In normal operation, current sink MOSFET 24 operatesin its saturated mode of operation controlling a constant level ofcurrent independent of its drain-to-source voltage. As a result of thesimultaneous presence of a source-drain voltage and current, power isdissipated in MOSFET 24. Continuous measurement of the drain voltage ofcurrent sink MOSFET 24 is required for two purposes—to detect shortedLEDs and to facilitate feedback to the switch mode power supply (SMPS)9. The presence of a shorted LED is recorded in an LED fault circuit 27,and feedback to SMPS 9 is effected by a current sense feedback (CSFB)circuit 26.

In summary, current sink MOSFET 24 requires three connections to thecontrol IC 6, specifically a source connection for current measurement,a gate connection for biasing the device to control its current, and adrain connection for fault and feedback sensing. These three connectionsper current sink MOSFET and hence per channel are depicted in FIG. 2A ascrossing an interface 28 between the discrete devices and a control IC.Even in the schematic circuit diagram of FIG. 2B, where cascode clampMOSFET 22 is eliminated and current sink MOSFET 24 must sustain highvoltages, illustrated by “HV” integral diode 23, each channel stillrequires three pins per channel crossing interface 28. This 3-pin perchannel requirement explains the need for high-pin count package 6 shownin FIG. 1. For a sixteen-channel driver, 3 pins per channel require 48pins for the output pins on the control IC. Taking into account the SPIbus interface, analog functions, power supplies and more, a costly 64 or72-pin package is necessary. Worse yet, many TV printed circuit boardassembly firms are incapable of soldering packages with a pin pitch anysmaller than 0.8 or 1.27 mm. A 72-pin package with a 0.8 mm pin pitchrequires a 14×14 mm plastic body to provide the peripheral linear edgeneeded to fit all the pins.

One significant issue with multichip system shown in FIG. 1 is thattemperature sensing in interface IC 6 can only detect the temperature ofthe IC, where no significant power dissipation is occurring.Unfortunately, the heat is being generated in the discrete current sinkDMOSFETs 4, where no temperature sensing is possible. Without localtemperature sensing, any of the current sink MOSFETs 4A-4Q couldoverheat without the system being able to detect or remedy thecondition.

In summary, today's implementations for LED backlighting of LCD panelswith local dimming capability suffer from numerous fundamentallimitations with regard to cost, performance, features, and safety.

Highly integrated LED driver solutions require expensive large area dicepackaged in expensive high pin count packages, and concentrate heat intoa single package. This limits the driver to lower currents, due to powerdissipation resulting from the linear operation of the current sinkMOSFETs, and lower voltages, due to power dissipation resulting from LEDforward-voltage mismatch, a problem that is exacerbated for greaternumbers of series connected LEDs.

Multi-chip solutions combining an LED controller with discrete powerMOSFETs require high BOM counts and even higher-pin-count packaging.Having nearly triple the pin count of fully integrated LED drivers, asixteen channel solution can require 33 to 49 components and a 72 pinpackage as large as 14 mm×14 mm. Moreover, discrete MOSFETs offer nothermal sensing or protection against overheating.

What is needed is a cost-effective and reliable backlight system forTV's with local dimming. This requires a new semiconductor chip set thateliminates discrete MOSFETs, provides low overall package cost,minimizes the concentration of heat within any component, facilitatesover-temperature detection and thermal protection, protects low voltagecomponents from high voltages and against shorted LEDs, flexibly scalesto accommodate a different number of channels and different sizeddisplays without requiring custom integrated circuits, and maintainsprecise control of LED current and brightness.

Ideally, a flexible solution would be scalable to accommodate a varyingnumber of channels and display panels of different sizes withoutrequiring custom integrated circuits.

SUMMARY

The above criteria are satisfied in an LED driver system according tothis invention. An LED driver IC comprises a functional latch and aserial lighting interface (SLI) bus, which itself comprises a prefixregister and a data register. The prefix register and the data registerare connected in series. The LED driver IC drives an external string ofLEDs.

Data identifying the functional latch are loaded into the prefixregister and data defining a functional condition in the LED driver ICare serially loaded into the data register, typically on successiveclock pulses. Responsive to the data in the prefix register a connectionis formed between the functional latch and the data register, andtypically upon the occurrence of a synchronism pulse, the data in thedata register is transferred to the functional latch.

In one embodiment, a number of LED driver ICs are arranged into an LEDdriver system for controlling a plurality of LED strings. The SLI bussesin the respective LED driver ICs are connected in series to form asystem SLI bus. Data is loaded serially into the system SLI bus suchthat the prefix register and data register in each LED driver IC containdata necessary to identify and control a functional latch within thatLED driver IC.

In one group of embodiments, each LED driver IC further comprises apreload latch, and the data from the data register is shifted into thefunctional latch in two stages, first from the data register to thepreload latch, and then from the preload latch to the functional latch.The transfer of data from the preload latch to the functional latches inall of the LED driver ICs can be performed at the same time, such thatthe functional latches in the various LED driver ICs are updatedsimultaneously. This feature helps to eliminate “flicker” when the LEDstrings controlled by the LED driver ICs are used in a flat paneldisplay, for example.

Each of the LED driver ICs may include a plurality of “channels,” eachchannel being represented by an external LED string and an internalcurrent sink MOSFET which controls the current in the external LEDstring. Moreover, a number of functional latches may be associated witheach channel, the functional latches being used to control, for example,the on-time of the current sink MOSFET, the size of the current in thecurrent sink MOSFET, a phase delay associated with the current sinkMOSFET, and settings to define when the LED string associated with thechannel is experiencing a fault condition.

In some embodiments, the LED driver IC comprises a latch that holds datato be transferred to the data register in the SLI bus. The data in thislatch may indicate the type of fault that the LED string or driver IC isexperiencing, for example, a shorted LED, an open-circuit LED string, oran over-temperature condition. After this data has been transferred todata register the SLI bus it is advanced back to an external interfaceIC as the next data sequence is loaded into the SLI bus. The interfaceIC, in conjunction with other elements of the system (e.g., amicrocontroller), can then take remedial action such as by turning offthe LED string.

In some embodiments the prefix register is subdivided into a channelprefix register and a function prefix register, the former holding datathat identifies a channel within the LED driver IC and the latterholding data that identifies a functional latch within that channel.

The SLI bus and LED driver IC of this invention are highly scalable anduse far less semiconductor area than prior art systems. For example, an8 bit channel prefix register, an 8 bit channel prefix register and a 16bit data register could theoretically be used to control 256 functionallatches in each of 256 channels with 65,536 levels of control, althoughin many embodiments a large number of these bits are not used.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a diagram of a prior-art multi-channel LED drivesystem for LCD backlighting using discrete DMOSFETs as integratedcurrent sinks and protective voltage clamps.

FIG. 2A is a schematic circuit diagram of an individual LED drivechannel using a discrete DMOSFET as a current sink with a protectivehigh-voltage cascode clamp DMOSFET.

FIG. 2B is a schematic circuit diagram of an individual LED drivechannel using a discrete high-voltage DMOSFET as a current sink withouta cascode clamp.

FIG. 3A is a schematic circuit diagram of a dual-channel high-voltageintelligent LED driver with serial bus control and a protectivehigh-voltage cascode clamp DMOSFET.

FIG. 3B is a schematic circuit diagram of a dual-channel high-voltageintelligent LED driver with serial bus control and a high-voltagecurrent sink MOSFET without a cascode clamp MOSFET.

FIGS. 4A and 4B are a schematic circuit diagram of a multi-channel LEDbacklight system comprising intelligent LED drivers with a current sensefeedback (CSFB) system and a SLI serial bus.

FIG. 5 is a simplified schematic diagram of the system shown in FIGS. 4Aand 4B, illustrating the significantly reduced bill-of-materials (BOM)that can be achieved using intelligent LED drivers with SLI serial buscontrol and a low pin-count interface IC package.

FIG. 6 is a block diagram illustrating “fat” SLI bus registers with acorresponding digital control and timing (DC&T) and analog control andsensing (AC&S) circuitry in a dual-channel intelligent LED driver.

FIGS. 7A-7C are a timing diagram for an SLI bus controlling multiple LEDdrivers.

FIG. 8 is a schematic circuit diagram of a four-channel high-voltageintelligent LED driver with an SLI bus and high-voltage current sinkMOSFETs without cascode clamp MOSFETs.

FIG. 9 is an illustration of a “fat” SLI bus for a four-channel LEDdriver IC.

FIG. 10 is a block diagram illustrating a prefix-multiplexed SLI busregister with corresponding digital control and timing (DC&T) and analogcontrol and sensing (AC&S) circuitry in a dual-channel intelligent LEDdriver.

FIG. 11 is a block diagram of a prefix-multiplexed SLI bus includingchannel and function decoding.

FIG. 12A is a schematic circuit diagram of a dual-channel high-voltageintelligent LED driver with prefix-multiplexed SLI bus control and asingle multiplexer.

FIG. 12B is a schematic circuit diagram of a four-channel high-voltageintelligent LED driver with prefix-multiplexed SLI bus control and asingle multiplexer.

FIG. 12C is a schematic circuit diagram of a four-channel high-voltageintelligent LED driver with prefix-multiplexed SLI bus control and adual multiplexer.

FIG. 13A shows an embodiment of a LED driver IC comprising a 4-channel8-function SLI bus decoder and a multiplexer.

FIG. 13B shows an embodiment of a LED driver IC comprising a 4-channel,8-function SLI bus decoder and a multiplexer.

FIG. 13C shows an embodiment of a LED driver IC comprising a 2-channel4-function SLI bus decoder and a multiplexer.

FIG. 13D shows an example of a magnitude comparator.

FIG. 13E shows an example of a function and channel decoder using ANDgates and a multiplexer.

FIG. 14 is a block diagram illustrating a prefix-multiplexed SLI busregister with a three-tiered register-latch architecture includingpreload and active latches.

FIG. 15 illustrates an SLI bus data sequence for a 16-channel systemcomprising eight LED driver ICs with four independent functions.

FIG. 16A is a flow chart showing the initialization and register updatealgorithms used for an SLI bus with multiple-function registers.

FIG. 16B is a flow chart illustrating the process of synchronous writingto multiple preload latches.

FIG. 16C illustrates a data sequence for a 16 channel, four-functionsystem with 8 LED driver ICs.

FIG. 17A illustrates a data sequence for updating only the PWM latchesin a 16-channel system.

FIG. 17B illustrates a data sequence for selectively updating channelsusing a “don't care” prefix condition.

FIG. 17C illustrates a data sequence for a mix of channel, function anddon't care instructions in a single SLI bus broadcast.

DETAILED DESCRIPTION

As described in the background section, existing backlight solutions forTVs and large screen LCDs are complex, expensive and inflexible. Toreduce the cost of backlight systems for LCD's with local dimmingwithout sacrificing safe and reliable operation clearly requires acompletely new architecture that at the very least eliminates discreteMOSFETs, minimizes the concentration of heat within any component,facilitates over-temperature detection and thermal protection, andprotects low voltage components from high voltages. While meeting theseobjectives may alone be insufficient to achieve a truly cost-effectivesolution able to meet the demanding cost targets of the home consumerelectronics market, such an improvement is a necessary first step towardthe goal of realizing low-cost local dimming.

The invention described herein enables a new cost-efficient and scalablearchitecture for realizing safe and economically viable LED backlightingsolutions of large-screen LCDs and TVs with energy efficient localdimming capability. The new LED drive system, functional partitioning,and architecture, overcome the aforementioned problems in cost,functionality and the need for high pin count packages. The newarchitecture is based on certain fundamental premises, including

-   -   1. The analog control, sensing, and protection of the current        sink MOSFET should be functionally integrated together in the        same IC with the current sink MOSFET itself, not separated into        another IC    -   2. Basic dimming, phase delay functions, LED current control and        channel specific functions should be functionally integrated        together in the same IC with the current sink MOSFET, not        separated into another IC.    -   3. System timing, system μC host negotiations, and other global        parameters and functions not unique to a specific channel should        not be functionally integrated together in the same IC with the        current sink MOSFETs.    -   4. The number of channels, i.e. current sink MOSFETs, in a        device package should be designed for thermal management, i.e.,        to avoid overheating, while meeting specified LED current,        supply voltage and LED forward-voltage mismatch requirements    -   5. Communication with and control of multi-channel LED driver        ICs should employ a low-pin count packages, ideally requiring no        more than three package pins in total on the central interface        IC as well as on each driver IC. The communication circuitry        should occupy only a small fraction of the driver IC's die area        and cost.    -   6. The level of functional integration in the interface IC and        LED driver ICs should be balanced to facilitate the use of        low-cost and low-pin count packages compatible with single layer        PCB assembly.    -   7. Ideally, the system should flexibly scale to any number of        channels without requiring significant redesign of the ICs.

The conventional architecture of FIG. 1, i.e. a centralized controllerdriving a number of discrete power MOSFETs, fails to meet even one ofthe above goals, primarily because it requires a central point ofcontrol, or “command center”, for all digital and analog informationprocessing. Necessarily, the command center IC must communicate with itsμC host as well as directly sensing and driving every current sinkMOSFET. This high degree of component connectivity demands a largenumber of input and output lines, necessitating high pin countpackaging.

Distributed LED Drive Architecture Overview

The solution of the problems of the prior art systems is a “distributed”system, one lacking in central control. In the distributed systemdescribed herein, an interface IC translates information obtained fromthe host μC into a simple serial communications protocol, sendinginstructions digitally over a serial bus to any number of “intelligent”satellite LED driver ICs. The implementation of an LED driver meetingthe above criteria is described in the above-referenced application Ser.No. 13/346,625. For purposes of clarity, the main concepts of thatapplication relevant to the subject matter of the present applicationare reiterated here, including a description of the interface and LEDdriver ICs, and the operation of the “serial lighting interface” or SLIbus—a protocol containing parameters specifically relevant tocontrolling LED lighting.

In addition to facilitating the control of the LED drivers, the SLI busis, in a preferred embodiment, connected in “daisy-chain fashion” backto the interface IC, so that fault conditions such as an open LED, ashorted LED, or an over-temperature fault occurring in any of the driverICs can be communicated back to the interface IC and ultimately to thehost μC. Each driver IC, in response to its SLI bus digitalinstructions, performs all the necessary LED driver functions such asdynamic precision LED current control, PWM brightness control, phasedelay, and fault detection, locally, without the assistance of theinterface IC.

Each LED driver IC also includes input and output pins for an analogcurrent sense feedback (CSFB) signal. CSFB lines connect the LED driverICs and the interface IC into a second daisy chain to allow theinterface IC to provide a feedback signal to the high-voltageswitch-mode power supply (SMPS), which dynamically regulates the voltagepowering the LED strings. With this architecture, a dual-channel LEDdriver IC can easily fit into a standard SOP16 package or any similarleaded package.

Along with its SPI bus to SLI bus translation responsibilities, theinterface IC supplies a reference voltage to all the LED driver ICsneeded to ensure good current matching, generates V_(sync) and greyscale clock GSC pulses to synchronize their operation, and monitorsevery LED driver IC for potential faults. It also facilitates voltage tocurrent translation of the CSFB signal into an ICSFB signal using anon-chip operational transconductance amplifier or OTA. The interface IC,even with all the above-described functionality, fits easily into anSOP16 package.

This application describes a method of improving the serialcommunication protocol and reducing the size of the circuitry associatedwith the physical interface of the SLI bus. These improvements arearticulated below, under the heading “Improved SLI Bus Interface andProtocol”. Initially, however, it is useful to describe the basicarchitecture of the serial bus controlled LED drivers, the video systeminterface IC and the first generation “fat” SLI bus protocol.

LED Driver with Integral Dimming and Fault Detection

An embodiment of an LED driver 50 according to this invention, formed inan LED driver IC 51, is shown in FIG. 3A. LED driver 50, which isintegrated in an LED driver IC 51, is a dual channel driver comprisingintegrated current sink DMOSFETs 55A and 55B, cascode clamp DMOSFETs 57Aand 57B with integral high-voltage diodes 58A and 58B, I-precise gatedriver circuits 56A and 56B for accurate current control, an analogcontrol and sensing circuit 60, and a digital control and timing circuit59. An on-chip bias supply and regulator 62 powers the IC.

One of the channels includes current sink DMOSFET 55A, cascode clampDMOSFET 57A and I-precise gate driver circuit 56A, which together drivean LED string 52A. The other channel includes current sink DMOSFET 55B,cascode clamp DMOSFET 57B and I-precise gate driver circuit 56B, whichtogether drive an LED string 52B.

LED driver 50 provides complete control of two channels of 250 mA LEDdrive with 150V circuiting capability and ±2% absolute current accuracy,12 bits of PWM brightness control, 12 bits of PWM phase control, 8 bitsof current control, fault detection for LED open and LED shortconditions and over-temperature detection, all controlled through ahigh-speed serial lighting interface (SLI) bus shift register 61, andsynchronized to other drivers by a common V_(sync) and grey-scale clock(GSC) signal. In one embodiment cascode clamp DMOSFETs 57A and 57B arerated at 150V circuiting capability, although in other embodiments thesedevices can be sized for operation from 100V to 300V. The current ratingof 250 mA is set by the power dissipation of the package and themismatch in forward voltage in the two LED strings 52A and 52B.

In operation, LED driver 50 receives a stream of data on its serialinput SI pin which is fed into the input of SLI bus shift register 61.The data is clocked at a rate set by a serial clock signal SCK suppliedby the interface IC (not shown in FIG. 3A). The maximum clock rate forthe data depends on the CMOS technology used to implement shift register61, but operation at 10 MHz is achievable even using 0.5 μm line widthprocesses and wafer fabs. As long as the SCK signal continues to run,data will shift into SLI bus shift register 61 and ultimately exit theserial out pin SO on its way to the next LED driver in the serial daisychain (not shown in FIG. 3A).

After the data corresponding to the specific LED driver IC arrives inSLI bus shift register 61, the interface IC momentarily stops sendingthe SCK signal. Thereafter, a V_(sync) pulse latches the data from theSLI bus shift register 61 into data latches contained within the digitalcontrol and timing circuit 59 and the analog control and sensing circuit60, the latches typically comprising flip flops or static RAM. Also atthe time of the V_(sync) pulse, any data previously written into thefault latches contained within the analog control and sensing circuit 60will be copied into the appropriate bits of SLI bus shift register 61.

When the interface IC resumes sending the serial clock SCK signal, theread and the write bits stored within SLI bus shift register 61 aremoved into the next driver IC in the daisy chain. In a preferredembodiment, the daisy chain forms a loop connecting back to theinterface IC. Sending new data into the daisy chain ultimately pushesthe existing data residing in the SLI bus shift registers on through theloop and ultimately back to the interface IC. In this manner theinterface IC can communicate with the individual LED driver ICs, settingLED string brightness and timing, and the individual driver ICs cancommunicate individual fault conditions back to the interface IC.

Using this clocking scheme, data can be shifted through a large numberof driver ICs at a high speed without affecting the LED current orcausing flicker, because the current and timing controlling the currentsink DMOSFETs 55A and 55B only changes upon each new V_(sync) pulse.V_(sync) may vary from 60 Hz to 960 Hz with the grey scale clockfrequency scaling proportionately, typically 4096 times the V_(sync)frequency. Since V_(sync) is slow, under 1 kHz, when compared to thefrequency of the SCK signal driving the SLI bus shift registers, theinterface IC can perform additional functions if desired, e.g. to modifyand resend the data, or query the fault latch multiple times within agiven V_(sync) pulse duration.

Commencing on the V_(sync) pulse, the digital control and timing circuit59 generates two PWM pulses to toggle the output of I-Precise gatedriver circuits 56A and 56B on and off after the proper phase delay andfor the proper pulse width duration, or duty factor D. I-Precise gatebias driver circuits 56A and 56B sense the current in current sinkMOSFETs 55A and 55B respectively and provide the proper gate drivevoltage to maintain a target current during the time I-precise gatedriver circuits 56A and 56B are enabled by the PWM pulses from digitalcontrol and timing circuit 59. Operation of the I-Precise gate drivercircuits 56A and 56B is thus similar to that of a “strobed” amplifier,being pulsed on and off digitally but providing a control function.

The peak current is set globally in all the LED drivers by the V_(ref)signal and by the value of I_(set) resistor 54. In a preferredembodiment the V_(ref) signal is generated by the interface IC.Alternatively, the V_(ref) signal may be supplied by a discrete voltagereference IC or as an auxiliary output from the AC/DC converter module

The specific current in any LED string can be further controlled throughthe SLI bus shift register by the Dot register, using an 8 to 12 bitword that adjusts the current sink DMOSFET's current to a percentagefrom 0% to 100% of the peak current value. In this manner, precisedigital control of the LED current, emulating the function of a currentmode digital-to-analog converter or “current DAC”, is possible usingthis architecture. In LCD backlighting applications, this feature can beused for calibrating the backlight brightness, for improving backlightuniformity, or for operating in 3D mode. In other cases, the LED driversmay be used to drive LED strings in signs and “wall-of-LED” display,generally comprising a mix of red, green and blue LEDs. In signageapplications the LEDs form the image so that no LCD is needed.

Referring to FIG. 3A, the current flowing through LED string 52A iscontrolled by current sink DMOSFET 55A and corresponding I-Precise gatedriver circuit 56A. Similarly, the current flowing through LED string52B is controlled by current sink DMOSFET 55B and correspondingI-Precise gate driver circuit 56B. The maximum voltage impressed uponcurrent sinks DMOSFETs 55A and 55B is limited by cascode clamp DMOSFETs57A and 57B, respectively. So long that the number of LEDs “m” is nottoo large, the voltage +V_(LED) will not exceed the breakdown voltagesof PN diodes 58A and 58B, and the maximum voltage on the current sinkDMOSFETs 55A and 55B will be limited to around 10V, one thresholdvoltage below the gate bias impressed on cascode clamp DMOSFETs 57A and57B by bias circuit 62, which in this embodiment is 12V. Bias circuit 62also generates a 5 V V_(cc) supply voltage to operate its internalcircuitry from the 24V V_(IN) input, using a linear voltage regulatorand a filter capacitor 53.

The drain voltages on current sink DMOSFETs 55A and 55B are monitored byanalog control and sensing circuit 60 and compared to an over-voltagevalue stored in a latch within analog control and sensing circuit 60.The over-voltage value is supplied from SLI bus shift register 61. Ifthe drain voltages of current sink DMOSFETs 55A and 55B are below theprogrammed values, the LED strings 52A and 52B are operating normally.If, however, the drain voltage of either current sink DMOSFET 55A orcurrent sink DMOSFET 55B rises about the programmed value, one or moreof LED strings 52A and 52B is shorted, and a fault is detected andrecorded for that specific channel. Likewise if either the I-Precisegate driver circuit 56A or the I-Precise gate driver circuit 56B cannotmaintain the required current in one of LED strings 52A or 52B, i.e. theLED string is operating “undercurrent”, this means an LED in one ofstrings 52A or 52B has failed open and the circuit continuity has beenlost. The corresponding channel is then turned off, its CSFB signal isignored, and the fault is reported. Sensing this “undercurrent” can beperformed by monitoring the output of the gate buffer devices withinI-Precise circuits 56A and 56B for saturation. This condition means thatthe buffer is driving the gate of the corresponding current sink DMOSFETas “full on” as it can. Alternatively, an undercurrent condition can bedetected by monitoring the voltage drop across the input terminals ofthe I-Precise circuits. When the input voltage to I-Precise circuits 56Aand 56B drops too low, the undercurrent condition has occurred, and anopen LED fault is indicated.

If an over-temperature condition is detected, a fault is reported andthe channel is left on and conducting unless the interface IC sends acommand to shut down that channel. If, however, the temperaturecontinues to rise to dangerous levels, analog control and sensingcircuit 60 will disable the channel independently and report the fault.Regardless of the nature of a fault, whether a shorted LED, an open LED,or an over-temperature condition, whenever a fault occurs an open drainMOSFET within analog control and sensing circuit 60 will activate andpull the FLT pin low, signaling to the interface IC and optionally tothe host μC that a fault condition has occurred. The FLT pin is asystem-interrupt signal informing the system IC whenever a faultcondition has occurred in one or more of the LED driver ICs. Normallythe line is held high, i.e. biased to V_(cc) through a high valueresistor. Whenever any LED driver experiences a fault condition, eitherfrom a shorted LED, an open LED, or an over-temperature condition, thespecific LED driver IC pulls the line low by enabling a groundedN-channel MOSFET such as MOSFET 219 in FIG. 6.

After FLT is pulled low, the interface IC 51 can query the LED driverICs through SLI bus interface 61 to ascertain what LED driver IC isexperiencing a fault condition and what kind of fault has occurred. Theinterface IC then communicates this information back to the hostmicrocontroller through the SPI bus interface enabling the system tomake decisions as to what action, if any, should be taken in response tothe fault occurrence. Since the FLT line on every LED driver IC employsan open drain MOSFET to actively pull the line low in the event of afault, in the absence of a fault the line is pulled high by a high-valueinternal resistor. As such, the FLT input to interface IC 101 in FIG. 4Bcan be paralleled with the interrupt input pin of the system μC, inwhich case any fault generated by the LED driver ICs not only informsinterface IC 101 of the fault condition, but can also generate aninterrupt signal in the μC, alerting it to the condition as well. Usingthe FLT line therefore provides an immediate indication of theoccurrence of a fault in an LED driver IC while the SLI bus and SPI busare used to gather additional information before deciding what action totake. In this way, full fault management is enabled without the need fora fully integrated driver IC.

Analog control and sensing circuit 60 also includes an analog currentsense feedback (CSFB) signal, which is equal to the lowest voltage amongthe drain voltages of the two current sink DMOSFETs 55A and 55B and thevoltage at the CSFBI input pin. The CSFB signal is passed to the CSFBOoutput pin. In this way, the lowest current sink voltage in LED strings52A and 52B is passed to the input of the next LED driver and ultimatelyback to the system SMPS to power the +V_(LED) supply rail.

In the manner described, LED driver 50 with integral diming and faultdetection capability is realized without the need for a centralcontroller IC.

An alternate implementation of an LED driver 80 meeting the abovecriteria is shown in FIG. 3B. LED driver 80, which is integrated in anLED driver IC 81, is a dual-channel driver with integrated current sinkDMOSFETs 87A and 87B but without cascode clamp MOSFETs. Instead DMOSFETs87A and 87B contain integral high-voltage diodes 88A and 88B that aredesigned to sustain high-voltages in when DMOSFETs 87A and 87B are in anoff condition. Typically, such a design is most applicable to operationbelow 100V, but it can be extended to 150V if required. As in the LEDdriver IC 50 of FIG. 3A, I-precise gate driver circuits 86A and 86Bfacilitate accurate current control, controlled by an analog control andsensing circuit 85, and a digital control and timing circuit 89. Anon-chip bias supply and regulator 84 powers the LED driver IC 81, inthis case from V_(cc), not from the 24V input as in driver IC 51. Asidefrom lacking cascode clamp DMOSFETs, driver IC 80 operates similar todriver IC 50, controlled through its SLI bus 90.

SLI Bus Interface IC and System Application

FIGS. 4A and 4B illustrate a distributed multi-channel LED backlightdriver system 100 in accordance with this invention. Shown is aninterface IC 101 for driving a series of LED driver ICs 81A-81H poweredby a common switch-mode power supply (SMPS) 108. Although only LEDdriver ICs 81A and 81H are shown in FIG. 4A, it is understood thatsimilar driver ICs 81B-81G are located between driver ICs 81A and 81H.Each of LED driver ICs 81A-81H has integral dimming and fault detectioncapability and is similar to the LED driver 80 shown in FIG. 3B. LEDdriver ICs 81A-81H are sometimes referred to herein collectively as LEDdriver ICs 81 or individually as LED driver IC 81.

Five common signal lines 107, comprising three digital clock lines (SCK,GSC and V_(sync)), one digital fault line (FLT), and one analogreference voltage line (V_(ref)) connect interface IC 101 to LED driverICs 81A-81H. A timing and control unit 124 generates the V_(sync) andGSC signals in synchronism with data from a host μC (not shown),received via serial peripheral bus (SPI) bus interface 122. Timing andcontrol unit 124 also monitors the fault interrupt line FLT toimmediately detect a potential problem in one of LED strings 81A-81Q. Avoltage reference source 125 provides a voltage reference to the systemglobally over the V_(ref) line in order to ensure goodchannel-to-channel current matching. A bias supply unit 126 powersinterface IC 101 through a V_(IN) line that is connected to a fixed +24Vsupply rail 110 supplied by SMPS 108. Bias circuit 126 also generatesregulated supply V_(cc), preferably 5V, to power LED drivers 81A-81H.The V_(cc) supply is filtered by a capacitor 102.

In this embodiment, each of LED driver ICs 81A-81H comprises twochannels of high-voltage current control, including current sinkDMOSFETs 87A-87Q with integral HV diodes 88A-88Q, I-Precise gate drivercircuits 86A-86Q, digital control and timing (DC&T) circuits 89A-89H,analog control and sensing (AC&S) circuits 85A-85H and serial lightinginterface (SLI) buses 90A-90H. Like the LED driver IC 81 shown in FIG.3B, the LED driver ICs 81A-81H lack a cascode clamp. Nonetheless thesystem 100 could also be fabricated with LED driver ICs similar to LEDdriver IC 51, shown in FIG. 3A, except that in that case the 24V V_(IN)supply, rather than V_(cc), would be used to power the LED driver ICsand bias the gates of the cascode clamp DMOSFETs.

An SLI bus 113, comprising signal lines 113A-113I, links the LED driverICs 81A-81H together in a daisy chain. In the embodiment shown in FIG.4B, the serial output terminal of SLI unit 123 (the SO pin of interfaceIC 101) connects via a signal line 113A to the SI input of LED driver IC81A, the SO output of LED driver IC 81A connects via a signal line 113Bto the SI input of LED driver IC 81B (not shown), and so on. At the endof the daisy chain, the SO output of LED driver IC 81H connects via asignal line 113I to the serial input terminal of SLI unit 123 (the SIpin of interface IC 101). In this manner, SLI bus 113 forms a completeloop, emanating from the interface IC 101, running through each of LEDdriver ICs 81A-81H and back to interface IC 101. Thus, shifting data outof the SO pin of interface IC 101 concurrently returns a bit string ofequal length back into the SI pin of interface IC 101.

SLI circuit 123 also generates the SLI bus clock signal SCK as required.Because the LED driver ICs 81A-81H have no addresses, the number of bitsclocked through the SLI bus must correspond to the number of devicesbeing driven, with one bit being advanced for each SCK pulse. The numberof devices being driven may be adjusted through software programming thedata exchange in SPI bus 122, or by hardware modification to interfaceIC 101. In this manner the number of channels within system 100 can bevaried flexibly to match the size of the display.

Modifying the registers in SLI bus circuit 123 to shift out fewer ormore bits, while relatively straight forward, still requires amodification in the manufacturing of interface IC 101. An alternativeapproach involves employing a programmable interface using software toadjust the driver for accommodating fewer or more LED driver ICs in thedaisy chain.

Current sense feedback to SMPS 108 relies on an analog daisy chain. TheCSFBI input pin of LED driver IC 81H is tied via CSFB line 112I toV_(cc), CSFB line 112H connects the CSFBO output pin of LED driver IC81H to the CSFBI input pin of LED driver IC 81G and so on. Lastly, CSFBline 112A connects the CSFBO output pin of LED driver IC 81A to theCSFBI input pin of interface IC 101. The voltage level of the CSFBsignal drops whenever it passes through one of LED driver ICs 81A-81Hdriving an associated LED string 83A-83Q that has a higherforward-voltage V_(f) than the LED strings associated with the LEDdrivers that the CSFB signal has previously passed through. Since LEDdriver ICs 81A-81H are arranged in a daisy chain, the CSFB signalratchets down as it passes from the LED driver IC 81H to the LED driverIC 81A. The CSFB signal in the final CSFB line 112A represents theforward-voltage V_(f) of the LED string 83A-83Q having in highest V_(f)in the entire LED array. Operational transconductance amplifier (OTA)127 converts the final CSFB signal in CSFB line 112A into a currentfeedback signal ICSFB 111, driving the voltage +V_(LED) on line 109 atthe output of SMPS 108 to the optimum voltage for flicker free lightingwithout excess power dissipation. CSFB lines 112A-112I are sometimesreferred to herein collectively as CSFB line 112.

The resulting system, shown in the simplified schematic diagram of FIG.5 achieves independent control and constant current drive of 16 LEDstrings 83A-83Q using only eight small LED driver ICs 81A-81H, allcontrolled by interface IC 101 through SLI bus 113 (including signallines 113A-13I) in response to a host μC 152 and a scalar IC 153. Onlytwo analog signals are present in the system, a common reference voltageV_(ref) on line 107, and the ICSFB signal 111 that controls the SMPS 108to produce the +V_(LED) output on line 109. As described above, theICSFB signal 111 is generated in the interface IC 101 from the CSFBsignals on lines 112A-112H. With few analog signals and no discreteDMOSFETs with high impedance inputs, the LED driver system 100 isrelatively immune to noise.

As shown in FIG. 5, the LED driver system 100 can be fabricated usingonly nine SOP16 IC packages (one interface IC and eight LED driver ICs)to drive 16 LED strings. Compared to the multi-chip LED driver system 1of FIG. 1, which uses 32 discrete MOSFETs and a 72 pin controller IC,the cost of fabrication is greatly reduced by the new architecture. Withsignificantly fewer components, system reliability is also enhanced.System 100 is also easy to deploy since the proprietary SLI bus protocolis used only between interface IC 101 and the satellite LED drivers81A-81H. The μC 152 communicates with the interface IC 101 and thescalar IC 153 via the SPI bus.

Without the cascode clamp DMOSFETs, the LED driver ICs 81A-181H in FIG.5 need only a 5V V_(cc) input. As a result, interface IC 101 can performthe 24V to 5V voltage conversion and distribute its 5V supply railV_(cc) to LED driver ICs 81A-81H. By eliminating the need for step-downregulation in the LED driver ICs 81A-81H, LED driver ICs 81A-81H can bemade smaller and the need an external filter capacitor can beeliminated, saving one package pin.

“Fat” SLI Bus Operation

To eliminate the necessity of high pin count packages, we discloseherein a new series communication bus and protocol specifically designedfor driving LEDs in backlight and display applications. The “seriallighting interface” bus, or SLI bus, uses a serial communications methodcomprising a clocked shift register with a serial input and output, anda clock to control the timing and rate of data transfer.

The operation of the SLI bus is illustrated in FIG. 6, which alsoprovides greater detail of the construction and operation of exemplaryembodiments of SLI bus shift register 90A, digital control and timing(DC&T) circuit 89A and analog control and sensing (AC&S) circuit 85Ashown in FIG. 4A. It will be understood that similar circuitry is usedfor SLI bus shift registers 90B-90H, digital control and timing circuits89B-89H and analog control and sensing circuits 85B-85H shown in FIG.4A. (SLI bus shift registers 90A-90H are sometimes referred tocollectively as SLI bus 90.) FIG. 6 shows a dual channel LED driver IC,comprising current sink DMOSFETs 87A and 87B and I-Precise gate drivercircuits 86A and 86B, but LED driver ICs controlling a different numberof channels may be implemented in a similar fashion.

The circuitry shown in FIG. 6 is mixed signal, combining both digitaland analog signals. SLI bus shift register 90A is connected to DC&Tcircuit 89A by several parallel data busses, typically 12 bits wide, andalso connected to AC&S circuit 85A by a variety of parallel data bussesranging from 4 bits to 12 bits wide.

The outputs of DC&T circuit 89A digitally toggle I-Precise gate drivercircuits 86A and 86B and current sink DMOSFETs 87A and 87B on and offwith precise timing synchronized by the V_(sync) and grey scale clock(GSK) signals. The current sink DMOSFETs 87A and 87B control the currentin two strings of LEDs (not shown) in response to analog signals fromAC&S circuit 85A, which control the I-Precise circuits 86A and 86B andhence the gate drive signals for current sink DMOSFETs 87A and 87B. Thegate drive signals are analog, and an amplifier with feedback is used toensure that the current in each of current sink DMOSFETs 87A and 87B isa fixed multiple of reference currents Iref_(A) and Iref_(B),respectively, which are also supplied by AC&S circuit 85A.

While FIG. 6 illustrates only current sink MOSFETs 87A and 87B, thecircuitry shown is compatible with either the cascode clamped LED driver50 shown in FIG. 3A or the high voltage LED driver 80 shown in FIG. 3B.To implement the cascode clamped version, two high-voltage N-channelDMOSFETs would be connected in series with current sink DMOSFETs 87A and87B, with the source terminals of the high-voltage N-channel DMOSFETstied to the drain terminals of the current sink DMOSFETs 87A and 87B,and with the drain terminals of the high-voltage N-channel DMOSFETs tiedto the anodes of the respective LED strings being driven.

In operation, data is clocked into SLI bus shift register 90A throughthe serial input pin SI at the rate of the SCK clock signal. Thisincludes 12 bit PWM on time data into registers 220A and 220B forchannel A and channel B, 12 bit phase delay data into registers 221A and221B for channel A and channel B, 12 bit “dot” current data intoregisters 222A and 222B for channel A and channel B, along with 12 bitsof fault information, comprising 8 bits into fault settings register 224and 4 bits into fault status register 225. Data within these registersare clocked out of the SO pin as new data is clocked in. Suspending theSCK signal holds data statically within the shift registers. The terms“channel A” and “channel B” are arbitrary and are only used to identifythe outputs and their corresponding data in the SLI data stream.

Upon receiving a V_(sync) pulse, data from PWM A register 220A is loadedinto D latch 211A and data from Phase A register 221A is loaded into Φlatch 212A of Latch & Counter A circuit 210A. At the same time, datafrom PWM B register 220B is loaded into D latch 211B and data from PhaseB register 221B is loaded into Φ latch 212B of Latch & Counter B circuit210B. Upon receiving subsequent clock signals on GSC grey scale clock,Latch & Counters 210A and 210B count the number of pulses in their Φlatches 212A and 212B and thereafter enable current flow in I-Precisecircuits 86A and 86B, respectively, illuminating the associated LEDstring in Channel A or B. The channels remain enabled and conducting forthe duration of the number of pulses stored in D latches 211A and 211B,respectively. Thereafter, the outputs are toggled off and wait for thenext V_(sync) pulse to repeat the process. DC&T circuit 89A thereforesynthesizes two PWM pulses to the gates of DMOSFETs 89A and 89B inaccordance with the data in SLI bus shift register 90A.

Also synchronized to the V_(sync) pulse, the data stored in Dot A andDot B registers 222A and 222B is copied into D/A converters 213A and213B, setting the current in DMOSFETs 87A and 87B. The D/A converters213A and 213B are discrete circuits that provide a precise fraction ofI_(ref) to set the currents in the associated LED strings.Alternatively, in a preferred embodiment DMOSFETs 87A and 87B have gatewidths divided into various sections using binary weighting, and theproper combination of these gate sections is charged to set the fractionof the maximum current desired. The reference current I_(ref), thatrepresents the maximum channel current, is set by R_(set) resistor 204and the V_(ref) input to a reference current source 217.

The fault detection circuitry includes LED fault detection circuit 215,which compares the source voltages of current sink MOSFETs 87A and 87Bagainst the value stored in fault latch circuit 214. The data in faultlatch circuit 214 is copied from the fault settings register 224 at eachV_(sync) pulse. Temperature detection circuit 216 monitors thetemperature of the LED driver IC 81, in which the circuitry shown inFIG. 6 is included. Detection of a fault immediately triggers open drainfault flag MOSFET 219 to turn on and pull the FLT line low, generatingan interrupt. The data in fault latch circuit 214 is written into thefault status register 225 on the following V_(sync) pulse.

Implementation of the dot function and digital-to-analog conversion isfurther detailed in the above-referenced application Ser. No.13/346,625. The application also includes detailed circuitimplementation examples of fault latch circuit 214 and LED faultdetection circuit 215, reference current source 217, and current sensefeedback (CSFB) circuit 218.

In the manner described, a serial data bus is used to control thecurrent, timing, and duration of a number of LED strings, as well as todetect and report the occurrence of fault conditions in the LED strings.The SLI protocol is flexible, requiring only that the data sent throughthe SLI bus shift register 514A matches the hardware being controlled,specifically that the number of bits sent per driver IC matches the bitsrequired by each driver IC, and that the total number of bits sent forone V_(sync) period matches the number of bits sent per driver IC timesthe number of driver ICs.

For example, in the circuitry of FIG. 6, the protocol including dotcorrection, fault setting and fault reporting comprises 88 bits per dualchannel driver IC, i.e. 44 bits per channel or LED string. If eightdual-channel driver ICs, controlling sixteen strings of LEDs, areconnected into a single SLI bus loop, the total number of bits shiftedout of the interface IC and through the SLI bus during each V_(sync)period is 8 times 88 or 704 bits, less than a kilo-bit. If the SLI busis clocked at 10 MHz, the entire data stream can be clocked throughevery driver IC and to every channel in 70.4 microseconds, or 4.4microseconds per channel.

While the serial data bus communicates at “electronic” data rates, i.e.using MHz clocks and Mbits-per-second data rates, the V_(sync), or“frame” rate used to control changing the image on the LCD display paneloccurs at a much slower pace, because the human eye cannot perceivechanging images quickly. While most people are unaware of flicker at 60Hz frame rates, i.e. sixty image frames per second, in A versus Bcomparisons, to many people 120 Hz TV images appear more “clear” than 60Hz TV images, but only using direct comparisons. At even higher V_(sync)rates, e.g. 240 Hz and up, only “garners” and video display “experts”claim to see any improvement, mostly manifest as reduced motion blur. Itis the large ratio between electronic data rates and the relatively slowvideo frame rate that makes serial bus communication to the backlightLED drivers possible.

For example, at 60 Hz, each V_(sync) period consumes 16.7 milliseconds,orders-of-magnitude longer than the time needed to send all the data toall the driver-ICs. Even in the most advanced TVs running with an 8×scan rate and in 3D mode, at 960 Hz each V_(sync) period consumes 1.04milliseconds, meaning up to 236 channels can be controlled in real time.This number of channels greatly exceeds the driver requirements for eventhe largest HDTVs.

The 88-bit per dual-channel “fat” protocol used in the SLI bus shiftregister 90A of FIG. 6 enables the interface IC to write or read all thedata in every register of every channel once during every V_(sync)period. The term “fat” refers to the content of the digital word used tocontrol each channel. The fat protocol requires that every variable andregister be specified in each packet of data transmitted from theinterface IC 101 to one of driver ICs 81A-81H, even if nothing changedfrom the prior data packet.

If a reduced data protocol is used, i.e. a protocol requiring fewer bitsper channel, sending data to every channel takes even less time. Sincethe fat protocol has no timing limitations because of the relativelyslow V_(sync) refresh rate, there is no data rate benefit. Using fewerbits in the serial communication protocol does however reduce the sizeof the digital shift registers and data latches in the driver ICs,reducing chip area and lowering overall system cost.

For example, an alternative data protocol for an SLI bus using 64 bitsrather than 88-bits is shown in the LED driver system 250 of FIGS.7A-7C,which includes LED driver ICs 251A-251H and an interface IC 252.As shown by the data sequence 253, the protocol still uses 12 bits forPWM brightness duty factor, 12 bits for phase delay, 8 bits for faultsetting, and 4 bits for fault status, but it omits the 12-bit Dotcorrection data. As a result, individual channel current setting andbrightness calibration of each LED string is not available in thisimplementation.

In LCD panel manufacturing, many manufacturers believe electronicallycalibrating a display for uniform brightness is too expensive and istherefore not commercially practical. Global display brightness canstill be calibrated by adjusting the value of a panel's current setresistors, such as set resistor 204 shown in FIG. 6, but uniformity inbacklight brightness cannot be controlled through the microcontroller orinterface IC. Instead, panel manufacturers manually “sort” their LEDsupply into bins of LEDs having similar brightness and colortemperature.

It should be noted that removing Dot data from the SLI bus protocol doesnot prevent overall display brightness control or calibration. Adjustingthe system's global reference voltage V_(ref) can still perform globaldimming and global current control. For example, in the system shown inFIG. 6, adjusting the value of V_(ref) affects the value of thereference current I_(ref) produced by reference current source 217. Ifthe reference voltage V_(ref) is shared by all of the driver ICs,adjusting V_(ref) will uniformly affect every driver IC and consequentlythe panel's overall brightness, independent of the PWM dimming control.

Returning to FIGS. 7A-7C, system 250 illustrates SLI bus datacommunication from a common system interface IC 252 to aserially-connected string of eight driver ICs 251A-251H. As shown, theSLI-bus serial output SO of interface IC 252 generates a sequence ofpulses and feeds those pulses to the input pin of driver IC 251Asynchronized to the clock pulses on serial clock pin SC. The SLI busserial output of driver IC 251A in turn sends its internal shiftregister data out of its SO pin and into the SI input pin of driver IC251B. Similarly the SO output of driver IC 251B connects to the inputpin of driver IC 251C and so on, collectively forming a “digital” daisychain. The last driver in the chain 251H, sends its SLI bus data fromits SO pin back to the SI pin of interface IC 252 to complete the loop.

In the operation of system 250, interface IC 252 sends data out of itsSO pin in response to instructions it receives on its SPI bus interfaceto the system's scalar or video IC. The data for every driver IC and LEDstring is clocked from the SO output of interface IC 252 to every driverIC 251A-251H in sequence. All data must be sent to all driver ICs withinone single V_(sync) period. Because the SLI bus is a serial protocol,the first data sent out from interface IC 252 represents the bits usedto control driver IC 251H. After 64 clock pulses the data destined fordriver IC 251H is present in the SLI bus shift register of driver IC251A. Interface IC 252 then outputs the data for driver IC 251G on itsSO pin synchronized to another 64 pulses on the SC clock pin. Duringthese 64 clock pulses, the data intended for driver IC 251H moves fromthe SLI bus shift register within driver IC 251A and temporarily intothe SLI bus shift register within driver IC 251B. This process isrepeated until at last, the data for driver IC 251A is output on the SOpin of interface IC 252 synchronized to the last 64 pulses on the SCclock.

In the last 64 bit “write cycle” of a given V_(sync) period, the datafor driver IC 251A is output from the SO pin and loaded into the SLI busshift register within driver IC 251A, the data for driver IC 251B movesfrom the SLI bus shift register within driver IC 251A and into the SLIbus shift register within driver IC 251B, and so on. Similarly, duringthis last 64 bits of the write cycle, the data for driver 251H movesfrom the SLI bus shift register within driver IC 251G into the SLI busshift register within driver IC 251H. Therefore, after 8×64 clockpulses, or 512 pulses on the SC pin, all of the data has been loadedinto the SLI bus shift registers of the corresponding driver ICs.Nonetheless, this data is not yet controlling the operation of the LEDstrings.

Only after the next V_(sync) pulse is supplied to the driver ICs, isthis newly loaded data copied from the SLI bus shift registers and intothe active latches of their corresponding driver ICs for controlling LEDbrightness, timing and fault management. Specifically, the data in theSLI bus shift register within driver IC 251A is copied into the activelatches affecting the operation of LED strings controlled by channels Aand B, the data in the SLI bus shift register within driver IC 251B iscopied into the active latches affecting the operation of LED stringscontrolled by channels C and D, and so on. Thereafter, the SLI bus shiftregisters are ready to be rewritten with new data for the next V_(sync)period. For the rest of the present V_(sync) period, the LED stringswill be controlled according to the data received prior to the lastV_(sync) pulse.

In this manner, the SLI bus data communication timing and clocking isasynchronous with the system's V_(sync) period and the V_(sync) pulsethat begins each V_(sync) period. That is to say, data from interface IC252 may be sent faster or slower through the SLI bus to the driver ICs251A-251H without the viewer of the display being aware of the ongoingmultichip interaction or the changing LED settings until the nextV_(sync) pulse comes along. The only timing requirement is thatinterface IC 252 is able to receive its instructions from the videocontroller or scalar IC via its SPI bus input, interpret thoseinstructions and output the channel specific information on the SO pinof its SLI bus for every driver IC within a single V_(sync) period. Asdescribed earlier, since the time needed to receive such instructions ismuch shorter than the V_(sync) period, this timing requirement imposesno limitations in the operation of the display.

FIGS. 7A-7C also illustrates that the Fault Set data register maycomprise various kinds of data, including data for adjusting the voltageused to detect a shorted LED (the SLED set code), setting a period oftime used to ignore the fault output from a shorted LED detect (shortedLED fault blanking), setting a period of time used to ignore the faultoutput from open LED detect (open LED fault blanking), and clearingpreviously reported open and shorted LED fault registers (open CLR andshort CLR). The SLI bus protocol is not limited to implementing specificfault related functions or features.

System 250 also illustrates the fault read back capability ofimplementing the SLI bus as a loop by connecting the SO output of thelast driver IC in the daisy chain (driver IC 251H) to the SI input ofinterface IC 252. While writing data from interface IC 252 into driverICs 251A-251H, the data residing within the SLI bus shift registersadvances through the daisy chain with each SC clock pulse. If the datawithin the SLI bus shift registers includes fault detection data writtenby one of driver ICs 251A-251H, then clocking that data through the loopand back into interface IC 252 facilitates a means by which a specificfault condition in one of the driver ICs 251A-251H can be reported backto the interface IC 252 and through the SPI bus to other components ofthe system. What interface IC 252 does with the fault informationdepends on its design and is not limited by the SLI bus protocol orhardware.

Multi-Channel Driver Capability & Limitations

While the examples shown describe dual channel driver ICs, the discloseddriver concept and architecture can be extended to greater number ofintegrated channels without limitation, except for power dissipation andtemperature restrictions of the driver ICs, packages, and printedcircuit board design.

One example of a multi-channel LED driver consistent with the disclosedarchitecture is illustrated in FIG. 8. Similar to the dual channeldriver of FIG. 3B, the quad LED driver IC 301 integrates four-channelsof high voltage current sink DMOSFETs 307A-307D with high voltage diodes308A-308D respectively. The current sink DMOSFETs 307A-307D arecontrolled by I-Precise gate driver circuits 306A-306D to control thecurrent in LED strings 303A-303D, calibrated to a current set resistor302. Driver IC 301, like the other driver ICs in the system, includes abias supply 304, an analog control and sensing (AC&S) circuit 310, and adigital control and timing (DC&T) circuit 309.

Aside from doubling the number of I-Precise gate driver circuits andcurrent sink DMOSFETs in the dual channel version, quad LED driver 301requires additional latches and circuitry in AC&S circuit 310 and DC&Tcircuit 309 to support the additional channels. Temperature protectioncircuitry does not require doubling as one per driver IC is sufficient.A significant area is also devoted to the SLI bus register 311, whichmust be doubled in size to support four channels rather than two.

An embodiment of four-channel SLI bus shift register 311 is shown inFIG. 9. Four-channel SLI bus shift register 311 includes 176 bits,double the data storage capacity of the SLI bus shift register 90A inthe dual channel system of FIG. 6. As a result, the entire data streamis double in length, including PWM, Phase, Dot and Fault data, but thereis no need to change the SLI bus protocol. Some of the fault data isduplicated, such as the temperature fault data stored in four-bit faultstatus registers 354 and 355, but the die area savings made possible byeliminating the redundant bits is typically not worth the complicationsimposed by changing the protocol.

Thus by utilizing the “fat” SLI bus protocol where all the data is sentfor every register in the daisy chain each time data is written from theinterface IC 101 to the LED driver ICs 81A-81H, the number of channelsintegrated into an LED driver IC can be extended simply by expanding theSLI bus shift registers 90A-90H proportionally to accommodate theappropriate number of integrated channels.

The fat SLI bus protocol, however, has several disadvantages.Specifically; the interface IC 101 remains heavily tasked to repeatedlyshift out on the SLI Bus 113 the same data to all driver ICs 81A-81H,even when the data has not changed. Also, the shift registers 90A-90H inthe multi-channel LED drivers 81A-81H are relatively large, and theyoccupy significant die area.

These disadvantages could by overcome in an SLI bus protocol thatreduces the magnitude of the data being sent so that only the latch datathat changes from video frame to frame needs be rewritten.

For example, in the LED driver 81 shown in FIG. 6, data loaded intoshift register 90A is written into or read from the latches 211A, 212A,211B and 212B in Latch & Counters 201A and 210B, respectively, D/Aconverters 213A and 213B, and fault latch circuit 214 at least onceevery V_(sync) period, even when nothing is changing. The repetitivesending and resending of unchanging data is inefficient, cumbersome andpotentially costly, wasting bus bandwidth, occupying the system withmundane tasks, and consuming silicon real estate with unduly large shiftregisters.

Improved Serial Lighting Interface Bus

The limitations and disadvantages of sending long digital words orinstructions over a serial bus can be circumvented by adding a “latchaddress” or “prefix” to the serial lighting interface bus protocol andembedding it in every SLI bus communication. When combined withcircuitry to decode and multiplex the SLI bus data, the embedded prefixinformation enables data to be routed only to specific targeted latches.

By sending data specifically only to latches requiring updates, the“prefix-multiplexed” or “slim” SLI bus architecture avoids the need forrepeatedly and unnecessarily resending digital data, especiallyresending redundant data that remains constant or changes infrequently.In operation, after an initial setup, only latches that require changingare rewritten.

Latches containing fixed data are written only once when the system isfirst initialized, and thereafter do not require subsequentcommunication through the SLI bus with the system IC. Because only thelatches that are changing are updated, the amount of data sent acrossthe SLI bus is greatly reduced. This method offers several distinctadvantages over the “fat” SLI bus method, namely:

-   -   the number of bits required to integrate a SLI bus shift        register is greatly reduced, saving die area and lowering cost,        especially in smaller (e.g. two-channel) LED driver ICs    -   the effective bandwidth of the SLI bus at any given clock rate        is increased because redundant data is not being repeatedly sent    -   the SLI bus protocol can be standardized with fixed word lengths        and functions without losing versatility

An example of a prefix-multiplexed SLI bus is shown in the embodiment ofLED driver IC 81 shown in the schematic circuit diagram of FIG. 10. Inaddition to the alternative LED driver IC 81, FIG. 10 also shows an SLIbus 410 containing a 16-bit prefix register 312 and a 16-bit dataregister 313, and a prefix decoder & multiplexer (mux) circuit 419. Thedata in data register 313 is routed to D latches 411A and 411B and Φlatches 412A and 412B in Latch & Counter A 410A and Latch & Counter B410B, respectively, to one of D/A converters 413A and 413B in digitalcontrol and timing (DC&T) circuit 402, or to a fault latch circuit 414in analog control and sensing (AC&S) circuit 403. These data transfersare made prefix decoder and multiplexer circuit 419 according to routingdirections contained in prefix register 312. Thus prefix decoder &multiplexer circuit 419 decodes the 16-bit word stored in prefixregister 312 and multiplexes the 16-bit data stored in data register 313into the appropriate D, Φ, or Dot latch in DC&T circuit 402 AC&S circuit403.

In the case of fault latch circuit 414, multiplexer 419 operatesbidirectionally, allowing the data stored in data register 313 to bewritten into fault latch circuit 313 or, conversely, allowing the datastored in fault latch circuit 414 to be written into data register 313.

In the embodiment illustrated in FIG. 10, the prefix-multiplexed SLI busprotocol uses a 32-bit word, i.e. the word stored in prefix register 312is 16-bits in length and the word stored in data register 313 is also16-bits in length, facilitating a variable with up to 65,536combinations to be uniquely written to or read from one of 65,536different latches. This offers a well-balanced compromise between theflexibility of addressing a large number of latches and maintaining ashort word length and small SLI bus shift register size and providesboth flexibility and expandability.

Despite facilitating a large number of combinations, not all the data inthe SLI bus 410 need be used. If LED driver IC 81 contains fewerfunctional latches and channels, fewer than 16 bits of the prefix wordneed be decoded. Likewise if less precision is demanded, fewer than 16bits of the data word need be transferred into the target latch. Forexample if the data contained in data register 313 is the PWM brightnessduty factor, 12 bits of data may be multiplexed and loaded into D latch411A, while if the data in register 313 is the LED current “Dot”setting, only 8-bits may be required by the Dot register associated withD/A converter 413A.

So in the prefix-multiplexed SLI bus, data is repeatedly written by theinterface IC 101 into the data register 312 and then multiplexed intoone of several functional latches in DC&T circuit 402 and AC&S circuit403, one bit at a time, in sequential fashion. In the embodiment of FIG.10 the data in data register 313 fans out into seven differentfunctional latches having different functional roles.

The “thin” prefix-multiplexed SLI bus 410 shown in FIG. 10 is in sharpcontrast to the “fat” SLI bus 90A shown in FIG. 6, wherein each registerin SLI bus shift register 90A has a one-to-one correspondence to afunctional latch in the LED driver IC 81, e.g. PWM A register 220Atransfers data into D latch 211A, Phase A register 221A transfers datainto Φ latch 212A, and so on. This one-to-one correspondence makesscaling the fat SLI bus architecture to larger channel count driver ICsproblematic and costly.

The fan out capability of the prefix-multiplexed SLI bus thereforeoffers a more versatile, lower cost approach to implement a multichannelLED drive IC that the fat SLI bus protocol. For this and other reasonsto be considered below, the prefix-multiplexed SLI bus represents animproved serial lighting interface bus protocol, architecture, andphysical interface.

A further improvement in the prefix-multiplexed SLI bus method isillustrated in FIG. 11. In this example, the 16-bit prefix register inSLI bus 311 is subdivided into two 8-bit prefix registers 312C and 312F,which store channel and function prefix information, respectively. Thedata register 313 remains unchanged. As shown, a prefix decoder 451 hastwo outputs, a channel select output 453 to select which LED channel isbeing controlled, and function select output 452 to select whichfunctional latch is being interrogated, i.e. which functional latch isbeing written to or read from.

Prefix decoder 451 selects one of the many channels 457 with a selectsignal in output 453; prefix decoder 451 then chooses the function to becontrolled (e.g., PWM or phase) with a function select signal in output452. A multiplexer circuit 454 then writes data from data register 313into a latch 455 that controls the analog or digital function 456 in theparticular channel 457 selected.

In this manner, any number of channels within a LED driver IC, i.e. anynumber of LED strings, can be controlled independently in real timefacilitating precise adjustment of each control function through ashared SLI bus 311, without the need for a large shift register or longdigital words.

In a preferred embodiment of this invention, the prefix (ch), prefix(fcn) and data registers within SLI bus 311 store a 32-bit wordcontaining 16 bits of data (i.e., 16 bits are unused). The word is thuscapable of addressing one of 256 different functions in any one of 256channels. Since the number of possible combinations greatly exceeds thenumber of channels and functions needed in a single LED driver IC, theimproved SLI bus protocol is not limited to the LED driver examplesdescribed herein. In a single LED driver IC, however, the number ofcombinations can be limited by decoding only a subset of the possibledigital latch addresses, reducing the size of the associated circuitryto a minimum. Since only one 32-bit shift register is required for eachLED driver IC, the extra, unused bits in the preferred 32-bit SLI busprotocol do not waste significant die area.

As an example of reducing the number of decoded bits, decoding the twoleast significant bits (LSBs) of the channel prefix register 312C, andthe two LSBs of the function prefix register 312F easily accommodate thequad LED driver 301 of FIG. 8 with only a 32-bit shift register, vastlysmaller than the 176-bit shift register 311 needed by the fat SLI busprotocol, as shown in FIG. 9. The 4-channel LED driver decoding isdescribed in the following table as one possible implementation.

Channel Select Decode Hex Bits Decoded Channel Selected 00 xxxx xx00Channel A 01 xxxx xx01 Channel B 02 xxxx xx10 Channel C 03 xxxx xx11Channel D Function Select Decode Hex Bits Decoded Function Selected 00xxxx xx00 PWM Brightness (D) 01 xxxx xx01 Phase Delay (Φ) 02 xxxx xx10Dot Correction 03 xxxx xx11 Fault Status & Reporting

FIG. 12A illustrates a variation of the embodiment of LED driver IC 81shown in FIG. 10, except that in the embodiment of FIG. 12A the prefixdecoder & multiplexer 419 has been split into a decoder 491 and amultiplexer 492.

The LED driver IC 81 shown in FIG. 12A provides complete control of twochannels of 250 mA LED drive with 150V circuiting capability and ±2%absolute current accuracy, 12 bits of PWM brightness control, 12 bits ofphase control, 8 bits of current control, fault detection for LED openand LED short conditions and over-temperature detection, all controlledthrough the high-speed SLI bus 410, and synchronized to other drivers bya common V_(sync) and grey-scale clock (GSC) signal. While current sinkDMOSFETs 87A and 87B shown in FIG. 12A are rated at 150V capability,these devices can be sized for operation from 100V to 300V as needed.The 250 mA current rating of DMOSFETs 87A and 87B is set by the powerdissipation of driver IC 81 and the mismatch in forward-voltage in theLED strings 83A and 83B. Above a 100V rating, it is advantageous tointegrate high voltage cascode clamp DMOSFETs in series with currentsink DMOSFETs 87A and 87B, whereby current sink MOSFETs 87A and 87B donot operate above the clamp voltage provided by the cascode clampDMOSFET, i.e. above 12V as described above in connection with FIG. 3A.

In operation, LED driver IC 81 shown in FIG. 12A receives a stream ofdata on its serial input (SI) pin which is fed into the SLI bus shiftregister 410. The data is clocked at a rate set by serial clock (SCK)signal supplied by the interface IC 101 (not shown). The maximum clockrate for the data depends on the CMOS technology used to implement SLIbus shift register 410, but operation at 10 MHz is achievable even using0.5 μm line-width processes and wafer fabs. As long as the SCK signalcontinues to run, data will shift into SLI bus shift register 410 andultimately exit the serial output (SO) pin on its way to the next LEDdriver IC in the serial daisy chain.

After the data corresponding to the specific driver IC arrives in SLIbus shift register 410, the SCK signal is momentarily stopped by theinterface IC 101. From the data in SLI bus shift register 410, decoder491 determines the channel and latch within DC&T circuit 402 or AC&Scircuit 403 that is to be controlled and directs multiplexer 485 toconnect the data register within SLI bus shift register 410 to thatlatch. The transfer of data from the data register in SLI bus shiftregister 410 to the target latch within DC&T circuit 402 or AC&S circuit403 occurs at the next V_(sync) pulse. The data latches in DC&T circuit402 or AC&S circuit 403 may comprise flip-flops or static RAM. In theevent that the decoder 491 instructs the SLI bus to interrogate thefault latch within AC&S circuit 403, then at the time of the V_(sync)pulse, any data previously written into the fault latch within AC&Scircuit 403 will be copied into the appropriate bits of SLI bus shiftregister 410.

A resumption of the SCK signal moves the read and the write bits withinSLI bus shift register 410 into the next LED driver IC in the daisychain. In a preferred embodiment, the daisy chain forms a loopconnecting back to the interface IC 101. Sending new data into the daisychain ultimately pushes the existing data residing in the SLI bus shiftregisters on through the loop and ultimately back to the interface IC101. In this manner, the interface IC 101 can communicate to theindividual LED driver ICs, setting LED string brightness and timing, andthe individual driver ICs can communicate individual fault conditionsback to the interface IC.

Shifting of the SLI bus data through the daisy chain connected shiftregisters advances one bit per SCK pulse. After 32 SCK pulses, the32-bit data or “word” for the last LED driver IC has been shifted out ofthe interface IC and into the first LED driver IC in the daisy chain,but is not yet residing in the intended LED driver IC. After 64 SCKpulses, the first 32-bit word moves from the first LED driver IC intothe second, and the next 32-bit word moves from the interface IC intothe first LED driver IC in the daisy chain. At this step, the SLI buswords still do not reside in their proper driver ICs. In a daisy chaincomprising “n” SLI bus registers in the daisy chain, only after “n”times 32 serial clock pulses SCK will the data finally be shifted intothe proper LED driver ICs. Interrupting the SCK pulses copies the datafrom the SLI bus shift registers into the preload latches, describedbelow in connection with FIG. 14. On the next V_(sync) pulse, the datais copied from the preload latches into the active latches and thechange in LED driver takes effect. Until then, the operation of the LEDdriver IC remains unaffected.

Because of the two-stage latch architecture, i.e. the combination of apreload latch and a second stage active latch (described below inconnection with FIG. 14), the prefix-multiplexed SLI bus communicationsprotocol and interface is robust and relatively immune from erroneouslyinstructing the LED driver ICs. For example, if the SCK pulse streamwere to momentarily freeze before the shifted data resides in thetargeted SLI bus shift registers and corresponding LED driver ICs, thenthe data will be copied from the SLI bus shift registers into thepreload latches but will not change the active latches data until theV_(sync) pulse occurs. So long that the SCK pulses resume operation andcomplete the shifting process before the V_(sync) pulse occurs, noerrors will occur from sporadic SCK pulses.

In cases where an LED driver IC comprises two or more LED channels, theshifting process must occur multiple times before the V_(sync) pulsemakes the changes active. For example the preload latches for all theodd numbered channels may be first loaded, followed by loading all thedata for the even numbered channels. This process is repeated for everyfunction until all the preload latches have been loaded at least once.After all the preload latches are loaded, the V_(sync) pulse initiates achange in LED driver IC operation by copying the preload latch data intothe active latches, whereby operation of the LED driver IC changes. Loadof data into multichannel LED driver ICs using the prefix multiplexedSLI bus protocol is further detailed later in this application.

Using this clocking scheme, data can be shifted through a large numberof driver ICs at a high speed without affecting the LED current orcausing flicker because the current and timing controlling the currentsink DMOSFETs 87A and 87B only changes upon each new V_(sync) pulse. Thefrequency of the V_(sync) pulses may vary from 60 Hz to 960 Hz, with thefrequency of the grey scale clock (GSC) signal scaling proportionately,typically at 4096 times the frequency of the V_(sync) signal. SinceV_(sync) is slow, under 1 kHz, when compared to the SLI bus clock SCKfrequency, the controller has flexibility to modify and resend the data,or query the fault latch multiple times within a given vertical-syncpulse duration.

Because in the slim SLI bus protocol the data register within SLI bus410 is not large enough to write to all of the functional latches withinDC&T circuit 402 and AC&S circuit 403 from a single SLI bus word or datapacket, the interface IC 101 must send multiple SLI bus packets to thedriver ICs to load all of the functional latches. This condition arisesat start-up, when all the latches need to be filled, or when the data inmore than one latch must be changed contemporaneously. If the datacontrolling the I-Precise gate driver circuits 86A and 86B is allowed tochange gradually in multiple steps over several V_(sync) periods, e.g.first changing the Φ latch, then changing the D latch, then changing theDot latch, etc., a viewer may be able to discern the step changes asflicker or noise in the video image. Several solutions to this potentialproblem are disclosed below, under the heading “Simultaneously LoadingMultiple Functional Latches”.

After the register data is loaded, commencing on the next V_(sync)pulse, DC&T circuit 402 generates two PWM pulses to toggle the output ofI-Precise gate driver circuits 86A and 86B on and off after the properphase delay and for the proper pulse width duration, or duty factor D.I-Precise gate driver circuits 86A and 86B sense the current in currentsink MOSFETs 87A and 87B respectively and provide the proper gate drivevoltage to maintain a target current during the time it is enabled byits PWM pulse. The I-Precise gate driver circuits therefore operate inthe manner of a “strobed” amplifier, being pulsed on and off digitallybut controlling the current in the LEDs as an analog parameter.

The peak current is set globally in all of the LED driver ICs by theV_(ref) signal and by the value of I_(set) resistor 82. The V_(ref)signal is, in a preferred embodiment, generated by the interface IC 101,or it may be supplied as an auxiliary output from the AC/DC convertermodule. In an alternative embodiment, channel-specific Dot correctioncan be eliminated, and V_(ref) can be modulated to facilitate globalcurrent control of the LED currents.

In driver ICs capable of channel-specific Dot correction, the current inany one LED string can be controlled through the SLI bus by the Dotlatch, preferably comprising an 8 to 12 bit word, that adjusts thecurrent sink MOSFET's current to a percentage from 0% to 100% of thepeak current value in either 256 or 4096 different steps, respectively.In this manner, precise digital control of the LED current, emulatingthe function of a current mode digital-to-analog converter or “currentDAC”, is possible using the newly disclosed architecture. In LCDbacklighting applications, this feature can be used for calibrating thebacklight brightness, for improving backlight uniformity, or foroperating in 3D mode.

The structure and operation of I-Precise gate driver circuits 86A and86B as well as AC&S circuit 403 are described in application Ser. No.13/346,625.

As shown, the current flowing through LED string 83A is controlled bycurrent sink DMOSFET 87A and corresponding I-Precise gate drive circuit86A. Similarly, the current flowing through LED string 83B is controlledby current sink DMOSFET 87B and corresponding I-Precise gate drivecircuit 86B. Without cascode clamp MOSFETs, the maximum voltageimpressed upon current sink DMOSFETs 87A and 87B is limited to operationbelow the breakdown voltage of high-voltage diodes 88A and 88B. Biascircuit 84 generates an internal chip bias voltage from a 5V V_(cc)input.

The drain voltages of current sink DMOSFETs 87A and 87B are alsomonitored by AC&S circuit 403 and compared to an over-voltage valuestored in its latch from SLI bus 410. If the drain voltages are below aprogrammed value, the LED strings 83A and 83B are operating normally.If, however, the drain voltages current sink DMOSFETs 87A and 87B riseabout the programmed value, one or more of LED strings 83A and 83B isshorted and a fault is detected and recorded for that specific channel.Likewise if one or more of the I-Precise gate driver circuits 86A and86B cannot maintain the required current, i.e. the LED string isoperating “undercurrent”, it means an LED has failed open and thecircuit continuity is lost. The channel is then turned off, its CSFBsignal is ignored, and the fault is reported. Sensing this“undercurrent”, can be performed by monitoring the output of theI-Precise gate driver circuits 86A and 86B for saturation, meaning thegate driver circuit is driving the gate of the current sink DMOSFET as“full on” as it can, or alternatively by monitoring the voltage dropacross the input terminals of the I-Precise gate driver circuit. Wheninput voltage to the I-Precise gate driver circuit voltage drops toolow, the undercurrent condition has occurred, indicating an open LEDfault.

If an over-temperature condition is detected, a fault is reported andthe channel is left on and conducting unless the interface IC 101 sendsa command to shut down that channel. If, however, the temperaturecontinues to rise to dangerous levels, AC&S circuit 403 will disable thechannel independently and report the fault. Regardless of the nature ofa fault, whether a shorted LED, an open LED, or over-temperature,whenever a fault occurs an open drain MOSFET within AC&S circuit 403will activate and pull the FLT pin low, signaling to the host μC 152that a fault condition has occurred.

AC&S circuit 403 also includes an analog current sense feedback (CSFB)signal, which monitors the drain voltages of the current sink DMOSFETs87A and 87B and the voltage at the CSFBI input pin of the LED driver IC81 for whichever of the three is lowest in voltage and passes thatvoltage to the CSFBO output pin of the LED driver IC 81. In this way thelowest drain voltage of any of the current sink MOSFETs, and hence theLED string with the highest forward-voltage drop is passed to the inputof the next LED driver IC and ultimately back to the system's SMPS 108to power the +V_(LED) supply rail 109.

In the manner described, a two-channel LED driver 81 with integraldiming and fault detection capability can be realized without the needof an interface IC.

FIG. 12B illustrates an extension of the disclosed prefix-multiplexedSLI bus control method to a four channel LED driver IC 501. As shown,LED driver IC 501 comprises four current sink DMOSFETs 507A-507D withcorresponding I-Precise gate driver circuits 506A-506D used toindependently drive four LED strings 503A-503D. In four-channel LEDdriver IC 501, DC&T circuit 509 and AC&S circuit 510 control fourI-Precise circuits 506A-506D, having double the number of functionallatches of a two-channel driver.

SLI bus shift register 512, which in this example is 32-bits long, isloaded multiple times to transfer requisite data to the various latchesin DC&T circuit 509 and AC&S circuit 510. If, for example, each channelcomprises four latches, namely D, Φ, Dot, and Fault, and the driver ICcomprises four channels, then SLI bus 512 must be loaded sixteen timesto set all the functional latches. Each time data is shifted into SLIbus shift register 512, decoder 513 interprets the prefix to select thetarget channel and function, whereby data is routed to the appropriatelatches in DC&T circuit 509 and AC&S circuit 510 through multiplexer511.

Because in the slim SLI bus protocol the data register within SLI businterface 512 is not large enough to write to all the functional latcheswithin DC&T circuit 509 and AC&S circuit 510 from a single SLI bus wordor data packet, the interface IC must send multiple SLI bus packets tothe driver ICs to load all the latches. This condition arises atstart-up when all the functional latches are first initiated, or whenthe data in more than one functional latch must be changedcontemporaneously. If the data controlling the I-Precise drivers506A-506D is allowed to change gradually in multiple steps over severalV_(sync) periods, e.g. first changing the Φ latch, then changing the Dlatch, then changing the Dot latch, etc., a viewer may be able todiscern the step changes as flicker or noise in the video image. Severalinventive solutions to circumvent this potential problem are disclosedbelow.

After the latch data is loaded, commencing on the next V_(sync) pulse,DC&T circuit 509 generates four independent PWM pulses to toggle theoutput of I-Precise gate drivers 506A-506D on and off after the properphase delay and for the proper pulse width duration, or duty factor D.I-Precise gate drivers circuits 506A-506D sense the current in currentsink MOSFETs 507A-507D respectively and provide the proper gate drivevoltage to maintain a target current during the times that they areenabled by the PWM pulses. Operation of the I-Precise gate drivercircuits is therefore like that of a “strobed” amplifier, being pulsedon and off digitally but controlling the current in the LEDs as ananalog parameter. LED current can be controlled through the SLI busthrough the Dot latches, globally through the V_(ref) voltage input, orthrough a combination of both.

FIG. 12C shows an alternative embodiment of a four-channel LED driver.LED driver IC 531 incorporates two 32-bit SLI bus shift registers 542Aand 542B to facilitate loading of two functional latches in parallel,i.e. simultaneously. Each of SLI bus shift registers 542A and 542B hasits own prefix and its own associated decoder 543A and 543B. The data isrouted through a dual-channel multiplexer 541 to the appropriatefunctional latches in DC&T circuit 539 and AC&S circuit 540. Otherwise,the operation of driver 531 is similar to that of driver 501 in FIG.12B. The advantage of using a dual SLI bus interface is that theinterface IC can load all of the functional latches in the LED driverICs in half the number of SLI bus write cycles. The actual system speedis similar in either approach, since the same number of bits iscommunicated on the SLI bus, i.e. a fixed number of 32-bit words or halfas many 64 bit words. The main advantage of this approach is theinterface IC does not have to manage many small SLI bus communications.

Decoder and Multiplexer Implementation

As illustrated in the circuit diagram of FIG. 11, key elements of theprefix-multiplexed SLI bus protocol and interface are the decoder andmultiplexer functions. Tasked with sequentially distributing data fromthe SLI bus shift register 311 to the appropriate functional latch, i.e.a latch 455, prefix decoder 451 interprets the prefix on each newdigital word and directs multiplexer 454 to copy data from SLI bus dataregister 313 into the corresponding functional latch 455.

One implementation of this decoder and multiplexer function is shown inFIG. 13A, where a prefix-multiplexed SLI bus 311 sequentiallydistributes data to numerous banks of functional latches 607 through adigital multiplexer 604 controlled by a decoder 601 and decoder keys605C and 605F. Each bank of functional latches and their associated setof latches 606 independently control separate I-precise gate drivercircuits driving distinct strings of LEDs (not shown). Specifically,functional latches 606 comprise channel A latches A1-A8, channel Blatches B1-B8, channel C latches C1-C8, and channel D latches D1-D8,together constituting 4 channels of 8 latches, controlling 32 functionalparameters in total. For the sake of clarity, only latch A1 is shown.

Multiplexer 604, used to route digital data between the SLI bus and thechannels and functions, operates in a manner analogous to a multi-polemulti-throw switch to facilitate multiple selectable data pathways fromSLI bus data register 313 to functional latches 606. In this example,multiplexer 604 comprises four 12-pole 8-throw, or 12P8T, switchescollectively controlled by decoder 601. As shown, only a fraction of thepossible combinations of the word stored in SLI bus shift register 311are actually selectable in this embodiment.

Specifically, because it has only 12 “poles” or parallel circuits,multiplexer 604 passes only 12 bits of data to latches 606 despite thefact that data shift register 313 contains a higher resolution 16-bitword. Using 12-bits from a 16-bit word decodes only 4,096 combinationsout of 65,536, or just 6% of the possible combinations. In most lightingapplications, however, eight to twelve bits are adequate to perform thefunction to the desired degree of precision. Typically, PWM brightness“D” and phase delay “Φ” require 12-bit precision, while dot correctionrequires only 8-bits.

Because multiplexer 604 addresses 4 channels with 8 positions, only 32latches are accessible despite prefix registers 312C and 312F beingcapable of addressing 65,536 different channels and parameters.Therefore, a quad-channel eight-position switch accesses 32combinations, or 5 bits selectable out of a sixteen-bit prefix, theimplementation using less than 0.05% of the prefix combinations. Becauseonly a small fraction of the data in shift register 311 is used,multiplexer circuit 604 occupies a very small die area using arelatively low number of logic gates and transistors.

Decoder 601 comprises 12 magnitude comparators, four for channel selectand eight for function select, along with 32 digital logic gates 603 todecode a portion of SLI bus prefix code 312 and thereby control thechannel selected by multiplexer 604.

Specifically, to be able to uniquely select four channels requiresdecoding a 2-bit prefix from channel prefix register 312C. Channeldecoding is performed by a magnitude comparator 602C which outputs alogic high or binary “1” whenever the two least significant bits inchannel prefix register 312C exactly match the two least significantbits in channel select code key 605C. The truth table for thetwo-channel magnitude comparator 602C is shown in Table 1:

TABLE 1 MC # Key (Ch) (LSB + 1) Key (LSB) SLI (LSB + 1) SLI (LSB) MC OutA 0 0 0 0 1 0 1 0 1 0 0 1 1 0 B 0 1 0 0 0 0 1 1 1 0 0 1 1 0 C 1 0 0 0 00 1 0 1 0 1 1 1 0 D 1 1 0 0 0 0 1 0 1 0 0 1 1 1

Since four combinations of the channel prefix code exist, there are fourdistinct magnitude comparators 602C with the same inputs but with fourseparate outputs, only one of which may have a logic “1” output at anygiven time. From the above, only a “00” code activates channel A, only a“01” code activates channel B, a “10” code is needed to select channelC, and a “11” code is needed to select channel D. In this manner, thereis only one SLI bus prefix code combination to select a given channel.In the 2-bit decoder shown, only the two least significant bits aredecoded, ignoring the higher magnitude bits altogether.

In a similar manner, in order to uniquely select one of eight functionallatches requires decoding a 3-bit prefix from function prefix register312F. Function decoding is performed by magnitude comparator 602F whichoutputs a logic high or binary “1” whenever the three least significantbits in function prefix register 312F exactly match the three leastsignificant bits in function select code key 605F. The truth table forthe three-channel magnitude comparator 602F is shown in Table 2:

TABLE 2 Key Key SLI MC # (LSB + (LSB + Key (LSB + SLI SLI MC (fcn) 2) 1)(LSB) 2) (LSB + 1) (LSB) Out 1 0 0 0 0 0 0 1 all other 0 2 0 0 1 0 0 1 1all other 0 3 0 1 0 0 1 0 1 all other 0 4 0 1 1 0 1 1 1 all other 0 5 10 0 1 0 0 1 all other 0 6 1 0 1 1 0 1 1 all other 0 7 1 1 0 1 1 0 1 allother 0 8 1 1 1 1 1 1 1 all other 0

Since eight combinations of the function prefix code exist, there areeight distinct magnitude comparators 602F with the same inputs but withfour separate outputs, only one of which may have a logic “1” output atany given time. From the above, only a “000” code activates function #1,e.g. duty factor D, only a “001” code activates function #2, e.g. phasedelay Φ, and so on. In this manner, there is only one SLI bus prefixcode combination to select a given function. In the 3-bit decoder shown,only the three least significant bits are decoded, ignoring the highermagnitude bits altogether.

Implementation of magnitude comparators can be performed in a variety ofways using Boolean logic, with the decoder 601 and channel and functioncode keys 605C and 605F hard wired, using counters, or stored inprogrammable memory elements including SRAM or even E²PROM. In oneembodiment of this invention, magnitude comparators are realized usingthe circuitry shown in FIG. 13D, illustrating a three-channel magnitudecomparator 631 comprising three dual-input exclusive NOR gates 632-634and a triple input AND gate 635. The implementation of an exclusive ORand its inverted counterpart, an exclusive NOR or XNOR gate is wellknown in the art (see, e.g., http://en.wikipedia.org/wiki/XOR_gate).

The logical truth table for the two-input XNOR function is to produce a“high” or logic “1” output whenever both its inputs are the same, eitherboth “0” inputs, or both “1” inputs. This is shown in Table 3:

TABLE 3 In A In B XNOR 0 0 1 0 1 0 1 0 0 1 1 1

For this reason, the exclusive NOR function is often logically used tocompare bits in two registers, in effect a digital version of acomparator. To utilize a logical XNOR gate, a multi-bit word must becompared bit versus bit using multiple XNOR gates. For example, to checkif two 8-bit digital words are identical, eight XNOR gates must be usedto check each bit separately. For the two digital words to match, allthe corresponding bits must match. By performing an eight-input logicalAND function on all the XNOR outputs, a match can be confirmed by apositive output of the AND gate.

This approach is shown in FIG. 13D in decoder 631, where three exclusiveNOR gates 632-634 are used to compare each bit in the SLI bus prefixregister against the corresponding bit in the channel or function selectkey code table 636. For example XNOR gate 632 compares the leastsignificant bit in the SLI bus prefix against the least significant bitin select code key 636 and outputs a logic “high” only if they match,either both having a logic “0” state or both having a logic “1” state.XNOR gate 633 similarly compares the next most significant bit i.e.LSB+1, of the SLI bus prefix to the corresponding bit in code key 636and outputs a “high” only if they match. In like fashion, comparator 634compares the next most significant bits in the two registers for amatch. Only if all three bits in the SLI bus prefix match will theoutput of AND-gate 635 go “high”, indicating that the two three-bitwords match exactly. Otherwise the output of AND-gate 635 and ofmagnitude comparator 631 will remain “low”.

For the sake of clarity, we use a reference numeral 637 to represent amultichannel magnitude comparator (MC) gate, where each pair of inputsis compared against one another for a match, and these results are thendelivered to a logical AND gate. A truth table for the three-input MCgate is described in Table 4, where “1” represents a match and “0”represents no match:

TABLE 4 LSB + 2 LSB + 1 LSB input pair input pair input pair MC Out 1 11 1 all other 0

The output of magnitude comparator 637 is “high” only when two digitalwords match exactly in their magnitude, confirmed bit by bit. In Booleanlogic, magnitude comparator MC 637 is described asMC={NOT(SLI_(LSB+2)⊕KEY_(LSB+2))}•{NOT(SLI_(LSB+1)⊕KEY_(LSB+1))}•{NOT(SLI_(LSB)⊕KEY_(LSB))}where SLI_(LSB+2), SLI_(LSB+1) and SLI_(LSB) represent the three leastsignificant bits of the SLI bus prefix being decoded, and KEY_(LSB+2),KEY_(LSB+1) and KEY_(LSB) represent three least significant bits of thechannel or function select code key. Algebraically, the plus sign withina circle is a Boolean symbol representing a logical XOR, and •represents a logical AND, where NOT is a logical inversion, i.e. acircled plus sign preceded by NOT represents a logical XNOR.

Returning to FIG. 13A, decoder 601 checks for one of four possiblechannels with MC 602C, and for one of eight possible functions with MC602F, and then performs a logical AND of these results using 32 separatedual-input AND gates 603. At any given time only one of AND gates 603will have a “high” output. This high output turns on a set of 12transmission-gate MOSFETs within multiplexer 604 connecting SLI dataregister 313 to the corresponding latch 606 in the desired channel. Likemultiplexer 604, decoder 601 is simplified in FIG. 13A for the sake ofclarity.

A more detailed description of decoder 601 and multiplexer 604 isillustrated in FIG. 13E, where the SLI bus channel prefix is decoded byfour magnitude comparators 641A-641D producing decoded channel bus 647,and where the SLI bus function prefix is decoded by eight magnitudecomparators 642A-642H producing decoded function bus 648. Collectively,these twelve bus lines feed a series of thirty-two dual-input logicalAND gates 643A1-643A8, 643B1-643B8, 643C1-643C8, and 643D1-643D8, whichin turn drive the MOSFETs comprising the multiplexer function.

Each AND gate 643 combines two inputs, one from one-of-four channel buslines 647, the other from one-of-eight function bus lines 648. Sinceonly one line of channel bus 647 is “high” at any one time and each ofthe four channels can have only one of eight lines in function bus 648“high”, then only 32 combinations are decoded. One such combination,decoded by logical AND gate 643A1 combines an input from channel A ofbus 647, i.e. the output of MC 641A, with a second input from the PWMbrightness control function “D” of bus 648, i.e. the output of MC 642A.As such this channel decodes the PWM brightness control for channel A.In a similar manner, the output of channel MC 641B and function MC 642Afeed AND gate 643B1, whose output uniquely selects PWM brightnesscontrol for channel B.

As shown, AND gate 643A2 decodes the phase function Φ for channel A. Ifthe SLI bus prefix selects this combination, the outputs of magnitudecomparators 641A and 642B will both be “high”, so that the output of ANDgate 643A2 is high. The output of inverter 644A in turn goes “low”, i.e.with a potential near ground, thereby turning on twelve P-channelMOSFETs 645A-645L. MOSFETs 645A-645L together act as a multichanneltransmission gate connecting SLI bus data register 313 to functionallatch 626A through data bus 649.

The multi-line connection between SLI data register 313 and functionallatch 626A occurs with a one-to-one correspondence between bits of equalsignificance, where the two corresponding LSBs are connected, the twoLSB+1 bits are connected and so on. As an example, MOSFET 645A connectsb₁, the LSB bit on the data bus, to the LSB in latch 626A. Similarly,MOSFET 645L connects b₁₂ on bus 649 to the most significant bit or MSBin latch 626A. Bus bits b₂-b₁₁ are likewise connected to theirrespective bits in latch 626A through ten intervening MOSFETs (notshown) with one-to-one correspondence. Despite the fact that SLI busdata-register 313 comprises a 16-bit digital word, the destination latch626A is only 12 bits wide. By copying from the LSB and up, the twelveleast significant bits b₁-b₁₂ are copied from data register 313 intolatch 626A while the four highest significance bits in shift register313 are ignored. The source register 313 and destination latch 626A neednot have identical bit width.

Similarly, AND gate 643D8 decodes the fault data for channel D. If theSLI bus prefix selects this combination the outputs of magnitudecomparators 641D and 642H will both be “high”, so that the output of ANDgate 643D8 is high. The output of inverter 644B in turn goes “low”, i.e.with a potential near ground, thereby turning on eight P-channel MOSFETs646A-646H. MOSFETs 646A-646H together act as a multichannel transmissiongate connecting SLI bus shift register 313 to functional latch 626Bthrough data bus 649. As in the prior example, multiple MOSFETs, in thiscase eight, interconnect register 313 and data bus 649 to thecorresponding bits within latch 626B.

Specifically MOSFET 646A connects b₁, the LSB bit on the data bus, tothe LSB in latch 626B. Similarly, MOSFET 645H connects b₈ on bus 649 tothe most significant bit or MSB in latch 626B. Bus bits b₂-b₇ arelikewise connected to their respective bits in latch 626B through sixintervening MOSFETs (not shown) with one-to-one correspondence. Despitethe fact that SLI bus data register 313 comprises a 16-bit digital word,the destination latch 626B is only 8 bits wide. By copying from the LSBand up, the eight least significant bits b₁-b₈ are copied from dataregister 313 into latch 626B while the eight highest significance bitsin shift register 313 (including the MSB) are ignored. The sourceregister 313 and the destination latch 626B do not share identical bitwidth with one another or with latch 626A.

In this manner, 16-bit SLI bus data can be directed to specificfunctional latches in an LED driver through a prefix-multiplexed SLIbus, even when the functional latches are not the same size as the SLIbus data. In contrast, FIG. 13A describes the operation of decodercircuit 601 and multiplexer circuit 604 as a high level constructcomprising four magnitude comparators for channel selection, eightmagnitude comparators for function selection, and 32 AND gates touniquely drive the transmission gate MOSFETs within quad 12P8Tmultiplexer switch 604. FIG. 13E therefore describes one possibleembodiment of the system shown in FIG. 13A.

To reiterate, the circuitry shown in FIG. 13A and the implementation ofthat circuitry shown in FIG. 13E illustrate a SLI bus multiplexed LEDdriver system independently controlling 32 parameters. Since 2⁵=32, only5 bits of the 16-bit SLI bus prefix registers 312C and 312F are requiredto provide the data required to control a 32 parameter LED driver. Theremaining 11 bits in the SLI bus prefix registers 312C and 312F areignored. While it is possible to reduce the size of the SLI bus shiftregister, the area savings in reducing the SLI bus shift register issmall compared to the size of the decoder. By only decoding thecombinations required, a flexible SLI bus protocol can be realized in arelatively small amount of silicon real estate.

Although this example of a prefix-multiplexed SLI bus uses a 16-bitprefix word stored in an 8-bit channel prefix register 312C and an 8-bitfunction prefix register 312F, it will be obvious to those skilled inthe art that a smaller number of bits may be employed, and the channelprefix and function prefix registers need not be equal in size. Forexample an 8-bit prefix register could utilize a 5-bit channel prefixregister to address 32 channels and only a 3-bit function prefixregister to address 8 functions. If it proves advantageous to support upto 256 separate channels, e.g. in a LED wall signage application, thechannel prefix register requires an eight-bit word. Using an additionalfour bits for function decoding supports 16 functions, generallyadequate for most LED lighting and display applications. The benefit ofreducing the aforementioned 16-bit SLI bus prefix down to a 12-bit shiftregister, however, offers a minimal savings in area. Also, a 12-bit wordis not a power of two, and therefore is inconsistent with binary andhexadecimal data sets and other industry-standard communicationprotocols.

So while reducing the size of the SLI bus prefix and associated shiftregister offers minimal savings while sacrificing flexibility andexpandability of the SLI protocol, minimizing the number of combinationsdecoded and reducing the size of the data bus being multiplexed offersreal cost savings potential.

Other decoding examples are included for the sake of completeness. FIG.13B illustrates a decoder 611 and a multiplexer 614 that drive sixteenfunctional latches 616 by decoding a 2-bit channel key stored in aregister 615C and a 2-bit function key stored in a register 615F withMCs 612C and 612F, where sixteen logical AND gates 613 drive a quad12P4T multiplexer 614, facilitating independent routing of 12-bit datato 16 functional latches. Using the prefix data stored in a channelprefix register 312C and a function prefix register 312F, the datastored in a data register 313 is routed to an appropriate one of latches616.

FIG. 13C illustrates a decoder 621 and a multiplexer 624 that driveeight functional latches 626 by decoding a 1-bit channel key stored in aregister 625C and a 2-bit function key stored in a register 625F withMCs 622C and 622F, where eight logical AND gates 623 drive a dual 12P4Tmultiplexer 624, facilitating independent routing of 12-bit data to 8functional latches. Using the prefix data stored in channel prefixregister 312C and function prefix register 312F, that data stored in adata register 313 is routed to an appropriate one of latches 626.

In the manner disclosed, a prefix-multiplexed LED driver can achievedynamic independent control of multiple strings of LEDs through aflexible serial communication interface. By multiplexing and routingdata contained in a serial communication shift register to variousfunctional latches with an LED driver IC, flexible control can beachieved without the need for expensive high-pin count packages, largearea shift registers, high data rate communication busses, or undulycomplex control.

Synchronously Loading Multiple Functional Latches

While the disclosed SLI bus communications interface and protocolfacilitates flexible multichannel LED drive in low pin-count packages,the aforementioned implementation is limited by its intrinsic “twotiered” register-latch architecture. In a two-tiered register-latcharchitecture, as shown in FIGS. 10, 11, 12A-12C, and 13A-13E, controldata exists only in two latches—a shift register within the SLI bus andthe active function latch. For example, in FIG. 11, shift register 313contains SLI bus communication data, and functional latch 455 containsfunction data used to control the operation of the LED driver IC.

In the previously described operation, data is copied from shiftregister 313 to latch 455 each time a V_(sync) clock pulse occurs. Bythat simple control method, loading multiple latches could take severalV_(sync) clock cycles. For example, in the first cycle the SLI bus datais written to PWM brightness “D” latch for channel A, in a second cyclethe data is written to the brightness “D” latch for channel B, in athird cycle the SLI bus data is written to the phase delay latch forchannel A, and so on. Considering each channel requires D, Φ, Dot, andFault settings, and Fault reporting, a dual-channel LED driver ICrequires at least ten V_(sync) cycles to load all the latches.

In two-tiered register-latch architectures, the latch data become activeimmediately upon loading in the latch at the time of the V_(sync) pulse.In this context, the term “active” means that the LED drive conditionsare affected by the change in latch data, i.e., the display backlightcondition has been altered, potentially causing visible changes in thedisplay's backlighting. So after channel A brightness data is loaded,waiting for another two V_(sync) pulses before the corresponding channelA phase data is loaded means that for some time period channel A willdrive its LED string at the proper brightness but with the wrong phase.

Writing the change into the functional latches in stages may causevisual aberrations in the backlight, including ghosting, flicker, etc.Unfortunately, sequential asynchronous loading of functional latches ina two-tiered register-latch system is intrinsically problematic. Sincethere is no temporary storage location to hold data, there is no meansby which to load data from the interface IC into the driver ICs exceptsequentially. Consequently, the ripple effect of the sequential changescannot be avoided. The SLI bus shift register cannot hold the databecause it must be used to clock in more data. The functional latchcannot be used because it is active and changes the LED drive conditionsas soon as it is loaded.

The solution to this quandary is to employ a three-tiered register-latcharchitecture as shown in FIG. 14. This architecture comprises a singleSLI bus shift register 313, multiple preload latches 655, and multipleactive functional latches 656, which are linked to control functions657. Control functions 657 may be analog or digital. In this embodiment,only one SLI bus shift register 311 is used to sequentially write datato multiple preload latches 655. Also, in embodiment of FIG. 14 aone-to-one correspondence exists between each preload latch 655 and eachactive latch 656, although this correspondence may not be present inother embodiments.

The structure shown in FIG. 14, with three tiers of registers/latches,is not meant to be exhaustive or limiting but merely, exemplary. Forexample, one LED driver IC can include more than one SLI bus register,whereby one SLI bus shift register addresses one set of preload latchesand a second SLI bus register addresses a second set of preload latches.In general however, for multiplexing to be economically beneficial, thenumber of active latches 656 should equal or exceed the number ofpreload latches 655; otherwise the prefix SLI bus architecture isactually less area efficient and more costly than the fat SLI busarchitecture.

Similarly, while in FIG. 14 the number of preload latches 655 equals thenumber of active latches 656, in other embodiments the number of preloadlatches 655 may be less than the number of active latches 656. Since theprimary function of a preload latch is to buffer data so as to preventthe data from affecting the condition of the LED drive while allowingthe data to be written into the associated active latch when required(not necessarily at the instant of a V_(sync) pulse), care must be takennot to create the aforementioned flicker problem by omitting preloadlatch 655 from some channels. Some functions are insensitive to theflicker problem, e.g. the Fault Set and Fault Status latches may bewritten and queried in real time without issue. In fact, the faultlatches do not need to be synchronized to the V_(sync) pulse, sincemanaging faults is not related to frame-by-frame image control andbacklight conditions. Likewise, the preload latch for the Dot functionmay be omitted if the Dot latch is only written once during startup. Insome instances, one preload latch maybe shared among several activelatches. For example, if the Dot function is only used as a globalsetting and not for channel-by-channel control, then one preload latchfor the Dot data can be used to write the active latches of multiplechannels for setting the LED current.

In summary, architecturally, the number of preload latches should beequal to or less than the number of active latches, and the number ofSLI bus shift registers should be less than the number or preloadlatches. In a preferred embodiment, at least the channel PWM brightnessfunction or “D” data, and the phase delay function or “Φ” data shouldinclude preload latches should include the three-tiered register-latchmethod comprising both active and preload latches.

Continuing with FIG. 14, the basic operation of the three-tieredregister-latch architecture involves shifting data into the SLI busshift register 311, writing the data from SLI bus data register 313 intoone of the preload latches 655 without altering the data in thecorresponding active latch at that time, and repeating the processes forevery channel and function until all the preload latches are loaded,then at some prescribed time, e.g. on the V_(sync) pulse, copying thedata from the preload latches 655 into their respective active latches656. Only when the active latch data changes, does the LED drivecondition change. So long that the V_(sync) pulse does not occur, thepreload latch can be written and rewritten multiple times withoutaffecting the LED drive condition.

A variety of timing options exist for writing data in the three-tieredregister-latch architecture, whether the data is loaded into the SLI busshift register 313 and copied into the preload latches 655 over severalV_(sync) cycles, or whether the data is all loaded within a singleV_(sync) cycle. Regardless, it is preferable that data be copied fromthe preload latch 655 into the active latch 656 at the beginning of aV_(sync) cycle so that PWM dimming and phase delay operation remainsconstant within a video frame and consistent with that of itspredecessor—the fat SLI bus version. In a preferred embodiment, all thedata is written to the various preload latches 655 within a singleV_(sync) period so that no special timing issues must be considered.

An example of a SLI bus communication sequence for loading every preloadlatch of every channel in a display LED-backlighting system within asingle V_(sync) cycle is illustrated in FIG. 15. The sixteen-channeldisplay system comprises eight LED driver ICs 701-701G driving sixteenLED strings in total, with two channels per LED driver IC and withindividual latches for controlling PWM brightness, Phase delay, Dotcurrent settings and Fault information. For convenience, the sixteenchannels are uniquely identified with channels A and B corresponding toLED driver IC 701A, channels C and D corresponding to LED driver IC701B, and so on up to driver 701G containing channels P and Q.

In the sequential labeling, channel O has been excluded to avoidconfusion between the letter “O” and the number “0”. In total, thenumber of latches comprises 8 driver ICs times 2 channels per driver ICtimes 4 latch per channel, for a total of 64 latches. Each driver ICcomprises two channels with four functional latches or eight latches intotal, consistent with dual-channel driver and decoding architectureshown in FIG. 13C. Because each driver IC contains only one SLI busshift register and eight functional latches, loading data into theentire backlight system requires a minimum of eight cycles, designatedby the sequential data sequences 702-709.

In example shown, the first data sequence 702 contains data intended forthe fault latches for channels Q, N, L, J, H, F, D and B in sequence,where the FLT data set is shifted into and through the SLI bus and thencopied into the corresponding fault preload latches. Next, a second datasequence 703 contains data for the fault latches for channels P, M, K,I, G, E, C and A in sequence, where the FLT data set is shifted into andthrough the SLI bus and then copied into the corresponding fault preloadlatches.

Next, in data sequence 704 the Dot data is loaded for channels Q, N, L,J, H, F, D and B in sequence, followed by data sequence 705 where theDot data for channels P, M, K, I, G, E, C and A is sequentially loaded.Similarly, in subsequent data sequence 706 the phase data is loaded forchannels Q, N, L, J, H, F, D and B in sequence, followed by datasequence 707 where the phase data is loaded for channels P, M, K, I, G,E, C and A. Finally in data sequence 708 the PWM data is loaded forchannels Q, N, L, J, H, F, D and B in sequence, followed by datasequence 709 where the PWM data for channels P, M, K, I, G, E, C and Ais sequentially loaded. In this manner, every functional latch in driverICs 701A-701G is loaded using a single shared SLI bus and multiplexed totheir appropriate latches using the appropriate prefix code, whereby allthe data is loaded within a single V_(sync) cycle. Subsequently, at somelater time, the V_(sync) pulse occurs, loading the preload latch datainto the active latches, changing the LED driving conditions and thedisplay backlight's operation.

It should be noted while the above sequence is described as writing datafrom the interface IC into its satellite LED driver ICs via the SLI bus,the protocol supports bidirectional communication from the LED driverICs back to the interface IC as well. For example, when the data in thedata sequence 702 is written into the FLT latches, the fault statusinformation can be copied from the driver ICs back into the appropriatebits in the data field of the SLI bus shift register. Then, when the FLTdata in data sequence 703 is shifted out to the LED driver ICs from theinterface IC, the fault data residing in the SLI bus shift register isshifted out the SO pin of the final driver IC in the daisy chain andback into the interface IC to be interpreted. As a result, the faultstatus data for channels Q, N, L, J, H, F, D and B are received by theinterface IC, not during SLI bus broadcast of data sequence 702, butduring the broadcast of the subsequent data sequence 703. In a similarmanner, fault status data for channels P, M, K, I, G, E, C and A are notreceived by the interface IC during SLI bus broadcast of data sequence703 but during the broadcast of the subsequent data sequence 704.

In this example, all of the preload latches in the entire system arewritten within a single V_(sync) cycle and the data thus written istransferred from the preload latches to the active latches when thesubsequent V_(sync) pulse occurs. While this process can be repeated forevery frame and V_(sync) pulse of the display's operation, after theinitial setup of the backlight driver system, resending redundant datais unnecessary and even burdensome.

A computationally and energy efficient alternative to rewriting everylatch in every V_(sync) cycle is illustrated in the flow chart and statediagram shown in FIG. 16A. In the flowchart, the backlight controlsequence comprises two phases, 751A where the backlight LED drivers areinitialized, and 751B where the backlight LED driver conditions arerefreshed. As in the sequence shown in FIG. 15, the initialization phase751A involves shifting the data 752A (including prefix and functionaldata) for a given active latch 754 into the SLI bus according to theserial clock SCK signal and then loading the appropriate preload latch753A. This process is repeated with the data for every active latch 754until all the preload latches 753B are loaded. The command to copy thedata from the SLI bus into a preload latch 753B can be embedded in theserial clock SCK waveform and therefore does not require a separatehardware solution or wire. After all the preload latches 753A have beeninitialized, the V_(sync) pulse informs the LED driver ICs to copy thedata into the active latches 754 and enable the change, thereby changingthe LED driving conditions and the display backlight's operation.

After initialization, only the functional latches that need to bechanged are updated and rewritten, i.e. refreshed. Update backlightphase 751B illustrates that during a data refresh, only specific latchesare rewritten by shifting data 752B into the SLI bus under control ofserial clock SCK signal, and then loading the data into only thespecific preload latches 753B for the channels and functions that arebeing updated. The other preload latches, i.e. the ones not beingupdated, remain unaltered. For example, the PWM and Phase data may beupdated for every channel on a frequent if not constant basis, but theDot data can remain unchanged unless the TV is changed from 2D to 3Dmode or vice versa. In this manner, the magnitude of data beingrepeatedly broadcast on the SLI bus is a small fraction of that sentduring the initialization.

In one embodiment of this invention, the instruction to copy the datafrom an SLI bus data register into a preload latch is based entirely onthe waveform of the SCK serial clock signal. In the timing diagram ofFIG. 16B, the serial clock SCK signal 771 is run in continuous fashionwhile data is loaded into LED driver ICs 701A-701H. Because the data isserial, the first data shifted into the SLI bus corresponds to thedriver IC farthest away from the interface IC, i.e. driver IC 701H,while the last data shifted into the SLI bus corresponds to the driverIC nearest to the interface IC, i.e. driver IC 701A. After the data hasbeen shifted into all of the SLI bus shift registers within driver ICs701A-701H, the SCK signal is held “high” for some duration t_(latch)774, after which the data from all the various SLI bus shift registersis copied into the preload latches 773 in parallel. The durationt_(latch) may be easily implemented with a timer and may for conveniencebe equivalent to the time equivalent to approximately 10 to 20 of theSCK pulses. For example, if the serial clock is running at 10 MHz, theneach SCK pulse is 0.1 μsec in duration. If the SCK signal is detected togo remain high, then after the t_(latch) timer counts to approximately 1μsec, the data from the SLI bus shift registers 701A-701H will latchinto the preload latches 773.

The timing of the t_(latch) timer is not critical. In fact the dataaccuracy of SLI bus is insensitive to interruption of the SCK signal. Iffor example the data were to be shifted only halfway through the serialchain when, for whatever reason, the SCK signal temporarily was hung upin a “high” state, then the high state would be interpreted as aninstruction to write the data into the preload latches. Since the wrongdata is present in the SLI bus shift register at that time, or moreaccurately the data is positioned incorrectly in the SLI bus registers,the wrong data would latch into the preload latches 773. Despite thistemporary communication error, no systems operation problem will resultso long that the V_(sync) pulse does not occur while the data is in theimproper SLI bus shift register.

Without a V_(sync) pulse, no preload latch data is copied into an activelatch. Assuming that the SCK signal resumes counting, the SLI bus datawould continue to shift through the serial bus until it reaches itsfinal destination LED driver IC shift registers, when after a durationof t_(latch), the proper data would be loaded from the SLI bus shiftregisters in driver ICs 701A-701H into preload latches 773, overwritingthe erroneous data. Since the entire event occurred well within a singleV_(sync) pulse, the fact that momentarily the wrong data had been loadedin to the preload latches is completely innocuous and unobservable inthe backlight's operation.

To shift the SLI bus data into the proper IC, a key aspect of SLI busoperation is that the number of bits broadcast on the SLI bus mustcorrespond to the corresponding LED driver ICs. In FIG. 16B, forexample, the number of bits on the SLI bus as a whole is equal to sum ofthe number of bits in the individual SLI bus registers in eightdual-channel LED driver ICs 701A-701H. Assume that the SLI bus registerin each of the eight driver ICs 701A-701H contains an 8-bit channelprefix register, an 8-bit function prefix register, and a 16-bit dataregister, for a total of 32 bits. To write SLI bus data into eight32-bit shift registers requires 256 SCK pulses. The first 32 SCK pulseswill load the data intended for driver IC 701H, the 33^(rd) to 64^(th)SCK pulses will load the data intended for driver IC 701G, and so on.Specifically, in the example of FIG. 16B, after the occurrence oft_(latch), duration data D_(B), D_(D), D_(F), D_(H), D_(J), D_(L), D_(N)and D_(Q) is copied from the data registers in the SLI bus in driver ICs701A-701H to their corresponding PWM preload latches PWM B, PWM D, PWMF, PWM H, PWM J, PWM L, PWM N and PWM Q, respectively.

Since each driver IC comprises two channels with two sets of preloadlatches, a second broadcast on the SLI bus is required to load the PWMpreload latches PWM A, PWM C, PWM E, PWM G, PWM I, PWM K and-PWM M. Thismust be repeated for every group of latches to be loaded.

Operation of a multichannel multi-latch sequence is further clarified inthe timing and flow chart of FIG. 16C, representing the output of theinterface IC controlling the SLI bus and all the satellite LED driverICs. In the example shown, timing waveforms 801 and 802 represent theSCK and V_(sync) pulses, with waveforms advancing in time from left toright.

During the SCK burst 803A the first set of PWM duration “D” data isshifted into the SLI bus shift registers. At the end of SCK burst 803A,the SCK signal is temporarily held “high,” during which time the SLI bus“D” data is copied into the preload latches P, M, K, I, G, E, C and A.During the next SCK burst 803B, the second set of PWM “D” data isshifted into the SLI bus shift registers. At the end of SCK burst 803B,the SCK signal is temporarily held “high” during which time the SLI bus“D” data is copied into the preload latches Q, N, L, J, H, F, D and B.

During SCK burst 803C and the ensuing SCK “high” phase data is shiftedinto the SLI bus and latched into preload latches P, M, K, I, G, E, Cand A, followed by SCK burst 803D and the following SCK “high,” duringwhich phase data is shifted into the SLI bus and latched into preloadlatches Q, N, L, J, H, F, D and B. Thereafter, during SCK burst 803E andthe following SCK “high” the Dot, i.e. LED current, data is shifted intothe SLI bus and latched into preload latches P, M, K, I, G, E, C and A,followed by SCK burst 803F and the following SCK “high,” during whichDot data is shifted into the SLI bus and latched into preload latches Q,N, L, J, H, F, D and B. Finally, during SCK burst 803G and the followingSCK “high” fault data is shifted into the SLI bus and latched intopreload latches P, M, K, I, G, E, C and A, followed by SCK burst 803Hand the following SCK “high,” during which fault data is shifted intothe SLI bus and latched into preload latches Q, N, L, J, H, F, D and B.

It should be noted that with the disclosed prefix-multiplexed SLI bus,the sequence of writing the first or second channel within a driver ICis entirely arbitrary. For example, it makes no difference if during SCKburst 803A the PWM data is for channels P, M, K, I, G, E, C and A or forchannels Q, N, L, J, H, F, D and B. Since the data in the preloadlatches is not displayed till it is copied into the associated activelatches at V_(sync) pulse 802, the order in which the preload latchesare loaded does not matter. The only requirements are that the dataintended for channels in the driver IC located farthest in the daisychain from the interface IC, i.e. channel P or channel Q, is writtenfirst and that the data intended for the channels in the driver IClocated closest to the interface IC, channel A or channel B, is writtenlast. Theoretically, it is possible in the SLI bus communication to mixup the first and second channels in alternating or arbitrary fashion,e.g. channel Q then channel M then channel K, but there is no benefit tothis practice while it makes the sequencing more difficult to check forerrors.

In the disclosed prefix-multiplexed SLI bus, the sequence by which thepreload latches are loaded within a given driver IC and channel is alsocompletely arbitrary. For example the preload latches that hold phasedata can be loaded before the preload latches that hold PWM duty factordata, and this can be done either before or after the Dot or fault dataare loading into preload latches. Thus the prefix-multiplexed SLI busand method of this invention affords tremendous flexibility in dynamiccontrol of multichannel multi-parameter LED drive.

At V_(sync) pulse 802, the data from the all of preload latches iscopied into the associated active latches, indicated by the arrows.Specifically, the data for PWM P and PWM Q, Phase P and Phase Q, Dot Pand Dot Q, and Fault P and Fault Q is written into the active latches ofdual-channel LED driver IC 701H; the data for PWM M and PWM N, Phase Mand Phase N, Dot M and Dot N, and Fault M and Fault N is written intothe active latches of dual-channel LED driver IC 701G; and so on.Likewise at V_(sync), the PWM, Phase, Dot and Fault data for the LEDdriver IC 701A that is closest to the interface IC is also copied fromthe preload latches into the active latches.

Refreshing LED Drive Conditions

After the active latches in the LED driver ICs have been fully loaded, asubset of the data can be sent to update the latches for dynamicchanges. One common dynamic change is to update the PWM brightnesssettings, a parameter that could change with every video frame. Such anupdate, shown in the SLI bus data sequence shown in FIG. 17A comprisestwo data sequences 851 and 852 that in two data broadcasts from theinterface IC load all of the PWM preload latches in LED driver ICs701H-701A. The data sequences 851 and 852 are thus a subset of the datasequences shown in FIG. 15.

Blank or “don't care” data may also be shifted into the SLI bus shiftregisters in channels not requiring updates, provided that the prefix isselected so as to not write to any latch in the driver IC. For exampleif only PWM P and PWM Q latches changed, then the data shifted throughthe SLI bus can comprise of 14 channels of “don't care” data and twochannels of PWM data, as shown in the data sequence of FIG. 17B. The“don't care,” or DC data, in the data field is ignored by choosing aprefix that doesn't physically address a latch in the IC, either bychoosing a channel select code that does not exist or a function selectcode that does not exist. For example, writing a channel code of0000-0100 or greater, 04 in hexadecimal, will select a channel codeabove the four integrated hexadecimal channels 00-03 in a four-channelLED driver IC and will therefore be ignored. Alternatively, writing afunction-select code of 0000-1000 or greater, 08 in hexadecimal, willselect a functional latch outside the eight latch hexadecimal range 00to 07 and will therefore be ignored.

Alternatively, a safe selection is to use the prefix FFFF,1111-1111-1111-1111 in binary, to choose a value well beyond allpracticable latch counts in even the largest systems. In an alternativeembodiment the code FFFF could be reserved to as a “don't care” command.The “don't care” function is necessary because, in a shift registerbased communication protocol, the right number of bits must be shiftedto shift the update data into the prefix and data registers of the SLIbus in the appropriate driver IC. Referring of the example shown in FIG.17B, loading a 32-bit word containing update data for PWM P into channel701H requires that seven 32 bit words, or 224 bits, be shifted into theshift register subsequent to the 32-bit word that contains the update tothe PWM P latch. The same is true for PWM Q, where a 32-bit update wordwith a prefix selecting the Q channel and the PWM functional latch mustbe followed by 224 bits to move the data into its corresponding driverIC 701H. It should be reiterated that in a dual-channel driver IC, itmakes no difference whether second channel is channel B, D, F, H, J, L,N and Q in the overall LED driver system. So shifting the right numberof bits into the SLI bus subsequent to shifting update data for aspecific latch onto the SLI bus is critical to selecting the rightchannel, function, and LED driver IC.

As a final point, updates can be mixed in a single SLI bus update solong as the number of bits broadcast is equal to the number of LEDdriver ICs times the number of bits in the SLI bus register of eachdriver IC.

For example, in the SLI bus communication sequence in FIG. 17C, a mix ofPWM Fault, Phase Dot and DC data is sent in broadcast sequence 891,comprising in total 8 channels times 32 bits or 256 bits shifted ontothe SLI bus. In the example shown, not only are different functionsmixed together into the same data stream, but also the channel selectedmay intermix A channel and B channel data into the same data stream. Forexample, the “A channel” data includes PWM C, Phase G, and PWM P datafor LED driver ICs 701B, 701G, and 701H respectively, the “B channel”data includes Fault J and PWM N data for corresponding LED driver ICs701E and 701G, and the data in driver ICs 701A, 701C and 701F indicatesa “don't care” drive condition. In short, in the embodiment describedabove, data for up to one (but not more than one) preload latch in anydriver IC can be included in any single sequence of data loaded into theSLI bus.

In the manner prescribed, updating LED driver conditions can beperformed using the disclosed prefix-multiplexed SLI bus protocolwithout resending the full set of latch information.

SLI Bus Flexibility

The disclosed prefix-multiplexed SLI bus is compatible with a variety offunctions not specifically disclosed herein, including the ability totoggle a given channel on or off, the ability to invert the PWM signal,and the ability to encode the CSFB feedback signal and embed it into theSLI bus protocol. The applications and functions described in thisdisclosure therefore should not be interpreted to limit the utility ofthe SLI bus in any way.

What is claimed is:
 1. A Light-Emitting Diode (LED) driver systemcomprising: a plurality of LED strings, each LED string of the pluralityof LED strings being associated with a respective channel of a pluralityof channels; and a Serial Lighting Interface (SLI) bus including aplurality of registers, the plurality of registers being seriallyconnected together in a daisy chain, each respective register of theplurality of registers being configured to store data that includeschannel data identifying a channel address, function data identifying afunction of a plurality of functions to execute at the channel address,and function value data identifying a value of the function, the SLI busbeing constructed to serially shift the function value data through theplurality of registers at a first rate, load the function value datainto at least one latch at a second rate that is less than the firstrate to change the value of the function in the respective channelresponsive to the channel address corresponding to the respectivechannel and the function data corresponding to a supported function of aplurality of supported functions included in the plurality of functions,and leave the value of the function unchanged responsive to at least oneof the channel address not corresponding to the respective channel andthe function data not corresponding to any one of the plurality ofsupported functions.
 2. The LED driver system of claim 1 furthercomprising a digital control and timing circuit coupled between the SLIbus and each LED string of the plurality of LED strings, the digitalcontrol and timing circuit including the at least one latch and anactive latch coupled to the at least one latch.
 3. The LED driver systemof claim 2 wherein the at least one latch is configured to load thefunction value data into the active latch at a third rate that is lessthan the second rate.
 4. The LED driver system of claim 1 wherein theLED driver system is included in a television display and the secondrate is a frame rate of the television display.
 5. The LED driver systemof claim 1 further comprising a respective current sink coupled to eachLED string of the plurality of LED strings, each respective current sinkconfigured to control a current through each respective LED string. 6.The LED driver system of claim 5 wherein the plurality of supportedfunctions includes a Pulse Width Modulation (PWM) brightness function tocontrol a duty cycle parameter of each respective current sink, a phasedelay function to control a phase delay parameter of each respectivecurrent sink, and a dot function to control a display dot pitchparameter.
 7. The LED driver system of claim 1 further comprising aninterface IC coupled to the SLI bus and configured to provide the datato the SLI bus and receive the data from the SLI bus after the data hasbeen serially shifted through the plurality of registers.
 8. The LEDdriver system of claim 7 wherein the plurality of supported functionsincludes a fault status and reporting function identifying at least oneof an open-circuited LED in at least one LED string of the plurality ofLED strings, a short-circuited LED in at least one LED string of theplurality of LED strings, and an over-temperature condition in at leastone LED string of the plurality of LED strings.
 9. The LED driver systemof claim 1 wherein loading each latch of a plurality of latches withrespective function value data is performed in an arbitrary order. 10.The LED driver system of claim 1 wherein function value datacorresponding to each supported function of the plurality of supportedfunctions is loaded into the at least one latch in an arbitrary order.11. A method for controlling at least one parameter of a respectiveLight-Emitting Diode (LED) string in a plurality of LED strings, eachrespective LED string corresponding to a respective channel of aplurality of channels, the method comprising: shifting data through aSerial Lighting Interface (SLI) bus at a first rate, the data includingchannel data identifying a channel address, function data identifying afunction of a plurality of functions to execute at the channel address,and function value data identifying an updated function valuecorresponding to the function; loading, by the SLI bus at a second ratethat is less than the first rate, the function value data into at leastone latch to replace a prior function value of the function with theupdated function value in the respective channel responsive to thechannel address corresponding to the respective channel and the functiondata corresponding to a supported function of a plurality of supportedfunctions included in the plurality of functions; and maintaining, bythe SLI bus, the function value data of the respective channel at theprior function value responsive to at least one of the channel addressnot corresponding to the respective channel and the function data notidentifying any one of the plurality of supported functions.
 12. Themethod of claim 11 further comprising maintaining the function valuedata of the respective channel at the prior function value withoutloading the updated function value data into the at least one latch. 13.The method of claim 11 further comprising loading, by the at least onelatch, the function value data into an active latch at a third rate thatis less than the second rate.
 14. The method of claim 11 wherein theplurality of LED strings is included in a pixelated display and thesecond rate is a frame rate of the pixelated display.
 15. The method ofclaim 11 further comprising controlling a respective current througheach LED string of the plurality of LED strings with a respectivecurrent sink, each respective current sink configured to modulate thecurrent responsive to receiving function data corresponding to at leastone supported function of the plurality of supported functions.
 16. Themethod of claim 15 wherein the plurality of supported functions includesa Pulse Width Modulation (PWM) brightness function to control an on timeof each respective current sink, a phase delay function to control aphase delay of each respective current sink, and a dot function tocontrol a dot pitch parameter of the plurality of LED strings.
 17. Themethod of claim 11 further comprising loading respective function valuedata into corresponding latches of a plurality of latches in anarbitrary order.
 18. The method of claim 11 further comprising loadingrespective function value data corresponding to each supported functionof the plurality of supported functions into the at least one latch inan arbitrary order.
 19. The method of claim 11 further comprisingcopying the function value data from the at least one latch to an activelatch, the active latch configured to replace the prior function valuewith the updated function value.
 20. The method of claim 11 wherein theplurality of supported functions includes a fault status and reportingfunction, the fault status and reporting function identifying at leastone of an open-circuit status of an LED in the plurality of LED strings,a short-circuit status of an LED in the plurality of LED strings, and anover-temperature condition in at least one LED string of the pluralityof LED strings.